From cb325bb819cc08a65f8baa35a314d84d71cdd63c Mon Sep 17 00:00:00 2001 From: Arjun Aditya Date: Sat, 15 Mar 2025 01:21:51 +0530 Subject: [PATCH 1/8] fix faq component for imgs --- apps/docs/content/help/faq.mdx | 8 +++---- apps/docs/src/components/Faq/index.tsx | 29 ++++++++++++++++++++----- apps/docs/static/img/gui/add-user.webp | Bin 0 -> 13142 bytes 3 files changed, 27 insertions(+), 10 deletions(-) create mode 100644 apps/docs/static/img/gui/add-user.webp diff --git a/apps/docs/content/help/faq.mdx b/apps/docs/content/help/faq.mdx index b671da13..78d519cc 100644 --- a/apps/docs/content/help/faq.mdx +++ b/apps/docs/content/help/faq.mdx @@ -20,12 +20,12 @@ Get quick answers to your related questions about Zerops from frequently asked q recommend visiting our pricing page to explore the options that best suit your needs. - Navigate to the main menu in the Zerop GUI (with your icon) and add a new user with the selected email to your team. + Navigate to the main menu in the Zerops GUI (with your icon) and add a new user with the selected email to your team.

Runtime Secret Variables

diff --git a/apps/docs/src/components/Faq/index.tsx b/apps/docs/src/components/Faq/index.tsx index 19defdf5..916f3e5c 100644 --- a/apps/docs/src/components/Faq/index.tsx +++ b/apps/docs/src/components/Faq/index.tsx @@ -12,11 +12,28 @@ export function FAQItem({ question, children }: FAQItemProps) { const [height, setHeight] = useState(0); useEffect(() => { - if (isOpen && answerRef.current) { - setHeight(answerRef.current.scrollHeight); - } else { - setHeight(0); + const updateHeight = () => { + if (isOpen && answerRef.current) { + setHeight(answerRef.current.scrollHeight); + } else { + setHeight(0); + } + }; + + updateHeight(); + // Add a small delay to handle image loading + const timer = setTimeout(updateHeight, 100); + + // Handle dynamic content changes + const resizeObserver = new ResizeObserver(updateHeight); + if (answerRef.current) { + resizeObserver.observe(answerRef.current); } + + return () => { + clearTimeout(timer); + resizeObserver.disconnect(); + }; }, [isOpen]); return ( @@ -36,11 +53,11 @@ export function FAQItem({ question, children }: FAQItemProps) {
-

{children}

+
{children}
diff --git a/apps/docs/static/img/gui/add-user.webp b/apps/docs/static/img/gui/add-user.webp new file mode 100644 index 0000000000000000000000000000000000000000..079068e5a8ce2a4c57d6d3c4435de802278068ee GIT binary patch literal 13142 zcmb`tWn5L=_6E9k(B0jg(%s$N(v5^jiwFwRpfpHH2}rkeBi#bhAdR3P-FIWW@A;o| zKim&@^IK~^^O<9eImTFX&Dd-$ML9V&ZUE4imD14D5HLUn0Duv8t%89!AV5)CT4MzR zRs}FtEL>fkz?cBw?Be03B`-y3U}!{%umeC~e_((KfLK_$yGm+ksN75cE${KapVMgo zbYGifySMc(|NjYLS=+c<0RTt?CT(f$ZsiQaH2?r@wsLjz004Mb7*FHv;d+k~U>Mg8 z<{%6g-ebGpxcMGi{>Ed!WOTHoVKVCgfQV{g;bsQ_=m#*K(#y&YW(NZkhB;iU9b8~o z0*1w$ogZ7n@Cz7bgvr4A#JIOFVEG?*?EV8=SXlmJ)55~;AN)HOm?o@a83%V)CyS@Q zD*u1poSi&j`TF%?fZb8;-4wK7B`z#)>yD3=?=dP2pSxJ9slzZf0Dz$mu;~6^e0xs? zT^NSRgBh*drD3@Q@L^cQ-AP;V53glyA)^e#q%hvr#Yye{+26|q+B(SH%fRvnPI2&1 z)PZ3_7%sGNm(~6w)9&_I>uA0y(g8k^GY%NRo}a z!M$(yIh?k(k&%UASnN?*HgX{c5!VykPvzf3f$R!#~__ zdu)L1FAc9>Rvdv%Sg+22GT;QOd%~~{Oy{o$dcZo2armeH*CPv^G-K?R_Kf8+R99&QtE z9PTUJ6x<5jteHcg+kfRv65v2f!NUr}95fDv9%o7OLX9AVGpzsC$EY{dNb^L~7|a};yza9sbk;$h?C0UP6h^kdhjZVq<#9+Z-> z6~l&7(Z!0Lm6D5tix&Xy*PnYC065b8wXT5hhyLY)mH|Mt?e6Zb>0eH%4FD?nVN*iG zzZ|0g0AQg2KwpEEr<>Prd(is=4mNXOz}`M0fE=KKEs1OZ7r+My0}_BNpaiG`I)EWy z3LCHXuyO7NcmsaGOCSV@1Y&?hAQgBAk;1e(ii~&=?JZ$uA0N;QE z;1sw5fj|f#G!PDm2t)y*1F?X(Kms5!kSs_Aqy;hrnS<;=E+9{kA1DYE35o-yg0ev$ zK$V~dPzR_VG!B{tt%7zyKS7sZ2pAQN3nl~8gCBqez>;8PunyP+YzKY<_65HJzXqp( zbHF9wI&cSg5IhB50e=IZz?N+k2tI@g!Uhq5NJG>iMi5(w8^j+H0ZD@7K*}JEu;)Ap zS%K_9E}-yG94IA}4K{)mpt?{i=o6?vGzyvuErixVyP=cNRp2u=~s z0L~818!iMc2`(S57On^OE^WY_!o$Pk!!yA1!`?+h_($;1;G^I(;LG9L;m6_E;7oXAqgR=BUvLoMS6pjht!BPinM`rg^Y#FfGmovgZv2jC2|UK8FCNu0`d_G3JNuf zAc`i61Ii1O6qE{-K9p6I3sh`WW>jfZV^mMn*Qf=k?WnV;M`&nh^k@=jMra;ruhBlB zb)hYxoulKRv!g4bTcZb{r=i!OPoRItK*FHIki;;>@Wn{NsKyw@*uzA^q{o!Tw7~So zOv7xzoWVT7!olLiQpa+}iozc`r~M!=@Wmc_QleubTj-G#k|1Hqxek;bvY3Bt+4 z>A~5+g~w&URm6RS8;M(rJA!+FhmFUBr-$c*mxkAZw}KDBr^i>scfx;zUxh!7e@Q?_ zAW2|D5Kd4=FhOueNJ1z`k0W+(W!a zf=ePyVnq@`QbjUH3MOSH)gpaHnoBxFdO}7{CQs%{_Li)RY>ynDT!Q=&c>;MW`3?mR zg&2hcMFK?|#V#ctr6i>jWeR0C(I~RW{WK)fF`ZwJvoabvgAS4Kj@YjV(iihn8ujF%)HF@%xTP{EMOKs76+CLmT^`%RzX%5)*RLuHdHoAHZQhf zwpDg~b`|zO_K)n}AJ9H9dJy}d_rWa(FNYIH9>+W6n*}d~_=G%!s)T+Bvk5y27YT2RFo@WQRl%xC zs`07|YIJHYY9G}Bbw%}f^+gQ^jVBsSn(&$$nrWJwTAW&bTD{sh+Gg5C+NU~FI&XC5 zbs2R%bvyMi^o;dB=$+}y=*Q`=7(6g|ZZK#_Z0KNEZ-ii^XOwSr@=*3+;=>JNUgHqs zX%hw$ACrDlVpAv67BdVp3$to-ICFjTBJ*ntb&DK}6H7(Qbjt%PX{%(bZ`Kml3D!F{ zqBe0hTehOMakkrbqIU6iJNDxCN%ngV(hjK(hmRBT}8G+5RAZOaIOQnt)dU8!zNv z6uv}$>G*OukRvcI@Hj|6sPPrqs~4}ipPNhkum8X-Yho_%qSZ7RRN@SM3BYPM5 z?lQ|E>r1wLc3lpAPEsy>u2=46o?c$>dx7^K@`>{!^KS}V3RViW3cEk>fA~;DTJ)wE zTYmme ze6;_#Qg2v4-k{Xb*(lst+r-{f&`i~w)`HjarWLvMRqI`wZ`(<`Yx`b@UB_CdS?7G0 zLD%PQ&F+yN<(|Gza-X_-C41ZYMEjcih58!?1O`41@(tDv@eb7v^A6XJ@Qu`s@{iV! z363?6i;TBUh);A(%1nOxtoV6wN^NRD5`pInjCH zg}_DcrT*pCmG?Emb;=FXP2;Wd?ZTb&-JPq2o5ioa00edi+u8!a&jJ8IGXwyfG1&g$ z;qUX|FA31^Gc62*{#^I;f8pO}$omG^9s($X?ddi5V7r?c0I0|V0D72x3}XP$Km!0B zK>*Cn{m=DF1$O5Cb?&^cz{AcJS=u+2&X#|g{!j7yObVm^`u*P}EE;ZZo_n4DQ^HRE zl!!DiZ$1MVAm*>&7?4=3Ooj?wZcYwWjpBI)HjITYyJ8B@k}knifC=sgD<@!w;%54uYxZrezet7thBlX@ZYX=EJwGkT?XD7UbkJ3 zZuFi%&=oD1FGzV%b7yk*_E!A!QVRjsoASeIDrWqI)wLk!$nyb&nu*$+pXJaO0G`2 z#4-J}z8=aop4!-byi_AxCH+^38RwQ`P363)=Ey>GHG-RWCDQy~_ z;e6Q~gjTP5Q6Ic7!?u&W8K}HveWRofp>CV};~s@JL%)1Hv~Khv`wt`1>{ibSltTVD z;Qvrk?%Q$bHkH<4?=pP$QE*p7HzZpO0#lQTQM3C#Po^rGz&Z;yW%(Fqtq^9~{+-m3 zRy$2LcZ4Fv&KTt27A-ju^G*)2qo`*{j9!D@HA2rqcwR*llFiThV|l=^kw3?lEI zItnwccpLt}&FwW4;D$m4WZF3pohG9{EcBMPeR3?4oaT1_T-b&u)|&G%%%>rsZ*}sn zh|Pa!Z8rM&Vb{7fcFd9?PM|Oybs>Vm=jpCFq8P&S(MXACaZ4teJMpSrlN)Zs3P#pI z$Fv_3aBcPQFRT;$8Li&LdX2Y_42JjEi-@5bOr5x_`7%HnzuSeo#idt>;%5=F(9nao zz0@VqEuap!2-c7r56^WqilXrtA)&Fl#ljN#O8{=Hj1NlPm4x=omNEMsXi zQb?nAIGvl0*$w>DySJcZ{3;J!Zcvga3OEHj5L74e=i8(D)A&o@%zy8 z)!9ENgzU{MGu&L-XDV%LhES3CCtbT#L;Qb6T|teQ@|?$FlEMHL{MKZT*5d_X?H=)7 zX3pRnKvf1UlQnsDru>Bg zGLlBCv0ubpeh>Nej+CJgb`jy`XN_wW%wUrs{;#J$Ou>$lQWU~Gz}QyUC3}jx_5R=Y zTghE&QLQ0}U2G`}tKd>55e1rXeKS33zLhovUoYg6Qnz?Xz$&h0=^lulme2OlKX?#h zG9`T_D1Rr?IV#(&>$v(dQCQTijLsIJ^}<0K%EEI4MgCW0`Cep`L4b0n(Q@8<+qmLJ zFnk0NX7{ZW;{Uv%e`gV^eIofEdygHV2FRt>K?bOL1!*}H6djr#8+;xegS8 zl?X!^w=p^sgQLo#XjJ1LUha0%n+~3Rax4@K zW1F-cU_q!|-nC#R`88WfGhd?1&ybRQRq!ymd8RduNg79!*}pl&fkhmM7mx%`=d;Y`cd3|Lhn5%A;RKwLQCWh&ILv<@j2PK6eN|{ zI__Z?k55?|afcn?7#BFc4H4YLdPP|)tj^(jO71>eMd?4&+2BsF&=Z=?(*n*{Op+Is z=3JEF2XY~wl*4|CrVO?ioljK(&d`Bg;U~mgdEnH)|m!X zDx4%1jzJv98>8koIOs8Qv~L}FgxXAhYU;nnJ`O8aYgG?(E&0(zs>1U8!Ln})-brIJ2^?EsGNi%Ftn2qj)8RH(Sl>FtcCy_x;@PG_ug=R;ny3$=r{L~6%V zXQW8AeN)Au@mf-NjDcR%TpSg?{?HA}>R@G!}Gi*>UbpEg&rcf9$J8eH5$@WLv$OB5L=B8JOu2YW6>#_vwa}mp4m7B zgA6*p?rgjY$oxs&KbgWa`5recD*rG@J+Ba+Gp$xkhG2Czx*sigo@I(ls$rT+*qXYU zgWA$D7}&(6JAEIU;9;cikk0isL;`_ob%HLw1u!xIb1xamDSe^pb0*I130?3gN+^0b z1NXhk;@jajx_3*FrIkkT<8nJ>Qg4;508TWa?k!A^F3TELOr&QkseB0QF;P&NHsx3T zm3Pq%d(;Sdx{um>ZTg!mu#`AxZI3d=qv=DlQ%isLn5V0b#t0BG7INp^7Q8-z?QW9l z&?@YZy%3+woER?lS~j*y-bh1v0^G^JjNv@@2wTXh(HNF2w%pd65kOt zqKIMt!FWA$&0xoT37bQ(-XIrf_SGoi~6! z)Im86>s`9P0Zm0*2V?X$x9MvRGD1_RDZyf>6giUakjhsUHC~ZlUuWI#y8r+|6j>l@ zX3qICx#-%~F&o(9jo))*6^vH+>{;y#AFoi`o{b#D^d=lVobnSAuRoJM11FvXcUcAlCmNwwhFjYKQtlV|p`E@6r1F;t)W zvMoMIV=HQIgY)%F!~)`K$r3_ngHG@6uH`2f?i%k_&w2(LYjo4854!{~C{Pp6yBBI2 zpO^|laU(|_3#o@@2OJuD$LFM`%UY$p4oG-!(nLp|G(=>#sIk(xu)D<-;VP-bx zYjwbDe9*io>kpQez{0Tzu;shNw_Bpe_EtEoWtm|jMvjc|h`@p`hcoq=d3A!+hZv7YSYUMbRCo{A^z8U~3On?PXRTTugueD2_rQ zH=segY>tyec63G~+`uqL2Q?UhzpE&*b}CM={HkKV^vqA@wqf{Fm$%YKuLIv$dD_ls zWCPDnlOdF1W{ye~v7xWfqJ=8irup4j(v zSNWka_6x~J}|4l1w{%&YAu>9C5keZk{fNzZ+Tj`I0o`e)0T+Q(V6OqdA$TeIb> z)F<`1g3%jbOIgdt3-Y3rMLl0pK>AZ}KsmRy-pKjf{IiH!`h}Gw2$?SjlHl%AarVoM z(z2O5nF@kp-FN+!XoU1Oh+q#|sUx)Gk$}~m5?qKD+w(MAvN4(hbT)VoHI^9u&8^cc z-atHjs+m}SL|N2|T|((n1N|_x#Hkj+>=Un8LInYn5qK^~`m_;2 z2M;Nc%YZ#U%%MUC1B!7bzO|G)?! z;-4e@(%S%aAs-)?^U=If=d6Bn-NIC-H*aI|5u0kncll$wh}zcq;Bkk2qNdju-rFa; zx0&8yO-m!EmSw|)I>Wu=sp!jthR6zp8yZ~G2Ac?kr}tqnEBg~>=Jf?mi6 zW`)bwKZtSI^!v{HFf)0jHqvHsmYFi9%Z!ML2a?Y2X?HZAAsqVjglnfTVSwNzc}MbB zfvui9@gKd$xDK=!^(txVZ{8m#mfgJBlnYRr!U}|^A7a(0~;QgscV}hgGQ5$ZNIFRcp^aYtGeT4JcaaD z!MBohsr6*?gD?v!KhioO6Rxh=(z`6Ze9~*yA^0%qhN4mQ{5K}vLYggZ#b3x16=L{% zho*LWhbQJyH~E4M5&dQ3@3s+#UY%g;fG@1B7emF=H-FyUp}-AxQKAhU?5?VJ4E7FP z*-DC__I#nwM15TRq?&fROE|qH0`RT#S{D2m!*a4C z5z-V>_|bTa-*EIv9TjK(r`kMmDoU9QpUG9~Pw--xIE{}d?ZP%C7nUi`SDOUeABp=V zllp`do)fqjYszIj}t=y```JQD_!>Jp_k1Byu=I@Wn+(-Vw5 z(bP9yqu8eUggb#)ll|^9Y?dQvvK^B7JZP1a4{_GvU|%P@(iuDc@CYM~?(K4gI~dxM z2rv>{gHzLAsK=rl*o|x{4w8S}%2a2^l5GXC41K8$dS`@vBqBlc9@KHIu{^Dm--0CB z6VY5?C6C016f>9A?iv@xz*sxBTaO|q(E9DLTAyW*52u+ptsE;d=}Sx`j%gXZ)Hf2@ z2Fw;G0va$T7x&j6nv@*E{LFCJ)H>F4V0=-+!lRsE2Lgrdq*M?ivdd3~1r|Kq+iUq} z?4@+dHMLf9N*AgWCgeWWYQQWn?0erVL2nawc|K> zu8eT_uc=5ExubV6S`X_Gbh6GxuS~mbgbn;{hSZV9kt41z1Ej7zu1Hj?o;>aps%7{p zcVHTg;_5)h@I;^2VnITQASc33?MQn;qkZUs;I~W8GMk63N^;03%E`Cv*4N0vHFsIw zwTTHYrRp9uIb!1y6iu%Rq|K1^+O0F^`$VJdo~~k!s>q_+$>79{LUBpnHd`S~E3B_? z$K|t>1*i(v{s*uq+vhbMQsZmiJZH7 z8U8KZo-KZ#x(}#7(U=p%>a+KlW)Dy%rdjVYS_#Z0$}VWo=Yr(l3}MD<@Zyg1 z8yr}y;PN0vuer$;4NafEEHC9sn{>Y^S6z9`wPOXW=j@OUYlaa}oIWg_YM z++6Ca=rde31OF}nVMQyQUW^DgP**T~sH?&$BN?dGbG9LIoi6^U6B!_hK~rPBT6DHF zccfW~g8l`fY0vxFt)i)YiID$p9l=A~l)se7^})*Vt!X_*RuAHGwnIF<%3Ch${y#+& zF3InD)Sohxm)^6;&NL~|?2CY;_MItzeZWo6;mups%0UUmnLN_(C36ms6-(foDds1n zK16zpUHFUFmiDGz#!d(y_xrb7XFuE#2X{n>%qC`8svJvHC#^r83lNo>Lw0!lsj6Bl z`dhZ3E>o6mWP)f0+!>AkdP86w&n^w0kjy$lXS>?$Wxy^N_L8{0Q?eg@|(R7IU zRQMwrrJ4Aihv7k4FYfn&?9JUuIXp}W)CCzVRV;JZMD{U`lKY4elyIQ=5VtAE!7GJf zzW2L3sAEi7fmY|tj&TDpyXILz<)#ia3}&gCg`bKnH1b?@^7(>E_#Oc|xInR2U# zPau+y8jSh)((Wc+w3=(0#u3e=Lb3Mr&gsRqH76KtY3Q#op*zlhuzznKkzNh$ULRN94%wZJPyi5Z#42b zwBX%Aety%C;3uc5Wl-%Ovzd%yRj-fqEIj0U$?fURL8O+NNafMuIC z?D`}76_wVc@n9V7s0+hJqDtmUv&Qvo%R`}9iY{g9+XD}(fhRr4W+j=Gotyi^)4?NAG~Nm)B|^wt zWgB~y34O*tzs;jxc#y9}TPC^ukQ-#rpj^rf!XuPnkM}30o5?2UAeU_sJPOTog7Z<~ zWR-cG_7XMLvRl{C1UkSlSF*Ch@b(SS(Zg^!nTlgLpC9WTDBh3uzUTJWp3bLJ8Oj}j z8ot^#Zd$39D`7sE#|$L%C0>`CIL~k0GjquzS1d87C2y%6>=IaUTU!b=Bzt`t=hWplkf`+VRG$gt*MKQ0iU5=MOrxa}W~1n3&qThPP@ za-xtDzne|A@nUJggXe1ZJdN2Nkxg0${?n2@qtrzUjF+9_*6jZNz zEUVo01*f~*!Ako}sI~Jvn#%%wbJk9sH0P6jymw7jEvMJ}HzZRNjCLz8MOZr?vD&ZH z5)ZFKq7Xv$0!|Nb%{PU5B8BwlKVYCw5KtT^em$@DDvkb3xM(N2F08!uY{()r-yDEs zE2v9dAcoB|Q$fw6pWBIz+ij}jS#mm+26y`yyvb%{@5yjbLX!oaTa$aOnuba^04ze{ zSe>s(3q6Gi?cglG7tjKiazo3GArm5RLe!U`n3NJP!BE8iE~qYQ1Qp_Z?Mqq1ITCO` zgvF-RR<)^ROm%l-`)z)4_EXMzLHziA@2Zm^qoj;-j7qb0%W0QP4eLZ0ajLMq!3MhM zVx79?x_#exY%YzQTvRj>F&B^Z|5mfn4BecGSx0_u-%q#z@Um>HOPEInN-tMMGs}(T zkJf2Hm^&i(G=h=`pR;ByfzTp3gA@s?a#|U-?SP9-pA$~=)oX2EW}N1czM0XteED)b zJX$5KjQ}9uuXf$b8XguH zdOC1^w`9uAjc%s23i12;qJj}`nfK!0MSIG=WGjfI z&>KD}Hml0)X))Onn-(2vZ0Hpcbto6v!VA#uB=a|Vj{Ad@?vq=X1BCvI?jmx5$_O{{ zvY+vK913C+Q}z)h(}H5l>w;)F*OAJ}9Q=!|?KDgKAic}teVPpCWQDKcsQt86s+l1~ z1SF~A%XeugKX-Q0ZFSZnT*R{*sq_TNaO2o=%ph;iN}_7%;b@=Wcpot z_E4h?XP(o|@m!X>AC4rC#a<#CZ_|RV7W&X$bA)BRZ=*+%(@k7=c6mk4du)-?49WNAhmBQjSgJQun2RJ=&d-{rb{hDsgFRi6|(z; zwe~U3UXDkRgwteQ;(Sb)NzoWqwQB}Btr^U3{*IeSw2l`3 zQy?c9LQD|e{uC7R33DgoqJq$B;2}%6STIketXFE=z9858*gW-C;riuxdx0L(^2^6; zfjkiURW*{#@!6a4CT^EDsmCLGjIs&-KHYKTn-$s_jtFsAYc`qYq&3M0rF2{oRt~}M z?tIJ72EBCw4EvW&8&OPs3f(E`)Yaz(+$@l~274qUdePZV%9hcQ1`U*IR#jOl%mX;uQInr$$J#y? zWWDQDzZiK4o(|Mhx%L-{v~k$F)}NRuWa}CjuKtitaimcPr8+%H>Yxd2?|&r^PDX~; zI$(lzOWUmcX*FWY3jbo^W;t<8=ElvHU< zAAMK*V(%y=?ru$oM^0s<^C5{I4SZ)CY=_CjNFwhkH^spesyqT|QI3q+$f4?d%;ejhFR`o7XM; z@O!cB=#70!+S3@oy>WU+^n-|bS26kww_ri6_p|3@z0JeW&;iPb*ILWyXRq;@%57FS z3~1e035F?(GPZ<+R3BLIJu5mmt!fP3H5o%)^Tth*f6@Stt$<7pL46fLdr`3 zvz;TdSIoM~5(msaupOw&%QA&ZfeBHkpTtb^LQK zq8*&G4Y}r|3coIN9&u9`AYW`se^jV>pUo6(IAcx75h_w~XPFVgYV zSMB}56G6ca{aom+=J@-Nj&D@?y7=1HS7J2!G!8b~-nE=>&}bN+OD>0~STC_TI4_~G zp7G{KtS_Di@{dRGocKkF*AlZSGu>)CEoiPdJ+d>HHOXTG)g6YhljstETdG0Hd#gkz zd3h)Q#)2n68_7$P#a-0&TQdGx7RteDk9I5~ZNMY`R|Hmt`Dmn*g?&1X-P+$f68SAu zdUYeo@<+;bx|_E+(25WQ@Zi5cASim_+Fh`^FGgy4{`t%1PA8iiC;m?Yw`d&>HQ9Vj zc{)xfIKRQNbBBDOv|1Bl`B?}aIe=oxiBBcBH;MODXum{JBw~RXcT_`W20P1;chh`f7<+_#;@ySX2gpR_rVIL-EO)9<3&}iYbx?*5sG8V{w)8 z_kjdkCC;?RA#p<+D)UzqtCkvyuGtix*^j0KA;}9*J*c#y;bG#()P=|zY*J>gcrMY^ zl6g}rmlt9k=|KhCvoBH+k~}wykAW-+7nMUJ$(ZJYOf5%twN~k=j3wfkt}*)q#njfA z4HhlAtVL|UYm}i+&BkIwJzJwshpOuzO6G+q!?$yU1-Ks<4hbLf8wtn}d-YGI4f}Z| zJSm7er|TI~8)>_2 zg6&JP$P^|b_YpoPji*6=#`d7}KZNSZ%ZL_?%kHO8SiU1kf0%U08S0z=#?-4SP;k3( z)vV`5EJ=i_3JL8u=wgSP=d|suC;(Ae0!3$RF|l|EVlh2PaCj8O8HQv|(xp-qXhjR@hdw=!r#vC9f)I%4V%!0OHkKI Date: Sat, 15 Mar 2025 01:43:11 +0530 Subject: [PATCH 2/8] fix tables --- .../docs/content/bun/how-to/env-variables.mdx | 31 +++++++++++++++--- .../content/deno/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../content/dotnet/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../content/elixir/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../content/gleam/how-to/env-variables.mdx | 32 ++++++++++++++++--- apps/docs/content/go/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../content/java/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../content/nginx/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../content/nodejs/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../docs/content/php/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../content/python/how-to/env-variables.mdx | 32 ++++++++++++++++--- .../content/rust/how-to/env-variables.mdx | 32 ++++++++++++++++--- 12 files changed, 323 insertions(+), 60 deletions(-) diff --git a/apps/docs/content/bun/how-to/env-variables.mdx b/apps/docs/content/bun/how-to/env-variables.mdx index 042988a9..222cf1ba 100644 --- a/apps/docs/content/bun/how-to/env-variables.mdx +++ b/apps/docs/content/bun/how-to/env-variables.mdx @@ -115,11 +115,32 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
### Reference a variable of another project service diff --git a/apps/docs/content/deno/how-to/env-variables.mdx b/apps/docs/content/deno/how-to/env-variables.mdx index 95f96631..c2ea4219 100644 --- a/apps/docs/content/deno/how-to/env-variables.mdx +++ b/apps/docs/content/deno/how-to/env-variables.mdx @@ -115,11 +115,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/dotnet/how-to/env-variables.mdx b/apps/docs/content/dotnet/how-to/env-variables.mdx index 85ff53c9..59009c88 100644 --- a/apps/docs/content/dotnet/how-to/env-variables.mdx +++ b/apps/docs/content/dotnet/how-to/env-variables.mdx @@ -136,11 +136,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/elixir/how-to/env-variables.mdx b/apps/docs/content/elixir/how-to/env-variables.mdx index f2858e23..bd4c5b3e 100644 --- a/apps/docs/content/elixir/how-to/env-variables.mdx +++ b/apps/docs/content/elixir/how-to/env-variables.mdx @@ -115,11 +115,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/gleam/how-to/env-variables.mdx b/apps/docs/content/gleam/how-to/env-variables.mdx index 7fa9f454..4def0e9c 100644 --- a/apps/docs/content/gleam/how-to/env-variables.mdx +++ b/apps/docs/content/gleam/how-to/env-variables.mdx @@ -115,11 +115,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/go/how-to/env-variables.mdx b/apps/docs/content/go/how-to/env-variables.mdx index 755883b4..76701caf 100644 --- a/apps/docs/content/go/how-to/env-variables.mdx +++ b/apps/docs/content/go/how-to/env-variables.mdx @@ -135,11 +135,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/java/how-to/env-variables.mdx b/apps/docs/content/java/how-to/env-variables.mdx index 21856739..4742fd24 100644 --- a/apps/docs/content/java/how-to/env-variables.mdx +++ b/apps/docs/content/java/how-to/env-variables.mdx @@ -135,11 +135,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/nginx/how-to/env-variables.mdx b/apps/docs/content/nginx/how-to/env-variables.mdx index a6d396ec..13191082 100644 --- a/apps/docs/content/nginx/how-to/env-variables.mdx +++ b/apps/docs/content/nginx/how-to/env-variables.mdx @@ -135,11 +135,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/nodejs/how-to/env-variables.mdx b/apps/docs/content/nodejs/how-to/env-variables.mdx index 9533838e..ea4dfd66 100644 --- a/apps/docs/content/nodejs/how-to/env-variables.mdx +++ b/apps/docs/content/nodejs/how-to/env-variables.mdx @@ -136,11 +136,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/php/how-to/env-variables.mdx b/apps/docs/content/php/how-to/env-variables.mdx index ffe2288e..118b36dc 100644 --- a/apps/docs/content/php/how-to/env-variables.mdx +++ b/apps/docs/content/php/how-to/env-variables.mdx @@ -135,11 +135,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/python/how-to/env-variables.mdx b/apps/docs/content/python/how-to/env-variables.mdx index 99ce45a8..2826afb0 100644 --- a/apps/docs/content/python/how-to/env-variables.mdx +++ b/apps/docs/content/python/how-to/env-variables.mdx @@ -135,11 +135,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service diff --git a/apps/docs/content/rust/how-to/env-variables.mdx b/apps/docs/content/rust/how-to/env-variables.mdx index 1e56dd03..5dfeb80f 100644 --- a/apps/docs/content/rust/how-to/env-variables.mdx +++ b/apps/docs/content/rust/how-to/env-variables.mdx @@ -134,11 +134,33 @@ You can reference another variable of the same service using `${key}` in your va ### Reference a local variable in another variable value -| Variable key | Variable value | Computed variable value | -| ------------ | ------------------- | ----------------------- | -| id | 12345 | 12345 | -| hostname | app | app | -| name | `${id}-${hostname}` | 12345-app | + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable keyVariable valueComputed variable value
id1234512345
hostnameappapp
name${'{id}'}-${'{hostname}'}12345-app
+ ### Reference a variable of another project service From f2f3f02b6a90d11342f35a763fd72eea851de70f Mon Sep 17 00:00:00 2001 From: Arjun Aditya Date: Sat, 15 Mar 2025 01:55:13 +0530 Subject: [PATCH 3/8] replace some images --- apps/docs/content/bun/how-to/build-process.mdx | 11 ++++++----- apps/docs/content/bun/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/deno/how-to/build-process.mdx | 11 ++++++----- apps/docs/content/deno/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/elixir/how-to/build-process.mdx | 11 ++++++----- apps/docs/content/elixir/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/features/pipeline.mdx | 2 +- apps/docs/content/gleam/how-to/build-process.mdx | 11 ++++++----- apps/docs/content/gleam/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/go/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/java/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/nginx/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/nodejs/how-to/build-process.mdx | 11 ++++++----- apps/docs/content/nodejs/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/php/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/python/how-to/deploy-process.mdx | 12 +++++++----- apps/docs/content/rust/how-to/deploy-process.mdx | 12 +++++++----- 17 files changed, 108 insertions(+), 81 deletions(-) diff --git a/apps/docs/content/bun/how-to/build-process.mdx b/apps/docs/content/bun/how-to/build-process.mdx index be092696..004aeeb2 100644 --- a/apps/docs/content/bun/how-to/build-process.mdx +++ b/apps/docs/content/bun/how-to/build-process.mdx @@ -4,6 +4,7 @@ description: Learn more about node.js' build process. --- import data from '@site/static/data.json'; +import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/bun/how-to/deploy-process.mdx b/apps/docs/content/bun/how-to/deploy-process.mdx index 712030c3..32ff39df 100644 --- a/apps/docs/content/bun/how-to/deploy-process.mdx +++ b/apps/docs/content/bun/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Bun Deploy process description: More about how node.js deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/deno/how-to/build-process.mdx b/apps/docs/content/deno/how-to/build-process.mdx index 6e5c2c78..20c50a05 100644 --- a/apps/docs/content/deno/how-to/build-process.mdx +++ b/apps/docs/content/deno/how-to/build-process.mdx @@ -4,6 +4,7 @@ description: Learn more about deno' build process. --- import data from '@site/static/data.json'; +import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/deno/how-to/deploy-process.mdx b/apps/docs/content/deno/how-to/deploy-process.mdx index 863d658d..da558b6d 100644 --- a/apps/docs/content/deno/how-to/deploy-process.mdx +++ b/apps/docs/content/deno/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Deno Deploy process description: More about how deno deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/elixir/how-to/build-process.mdx b/apps/docs/content/elixir/how-to/build-process.mdx index 1389bd7b..dd799ae7 100644 --- a/apps/docs/content/elixir/how-to/build-process.mdx +++ b/apps/docs/content/elixir/how-to/build-process.mdx @@ -4,6 +4,7 @@ description: Learn more about Elixir' build process. --- import data from '@site/static/data.json'; +import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/elixir/how-to/deploy-process.mdx b/apps/docs/content/elixir/how-to/deploy-process.mdx index 9050241b..6f9b3871 100644 --- a/apps/docs/content/elixir/how-to/deploy-process.mdx +++ b/apps/docs/content/elixir/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Elixir Deploy process description: More about how Elixir deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/features/pipeline.mdx b/apps/docs/content/features/pipeline.mdx index 110998e0..79a3f0ca 100644 --- a/apps/docs/content/features/pipeline.mdx +++ b/apps/docs/content/features/pipeline.mdx @@ -349,7 +349,7 @@ When you know that the running build is not correct and you want to cancel it, y lightImage="/img/gui/running-build.webp" darkImage="/img/gui/running-build.webp" alt="Running build" - style={{ width: '100%%', height: 'auto' }} + style={{ width: '100%', height: 'auto' }} />

diff --git a/apps/docs/content/gleam/how-to/build-process.mdx b/apps/docs/content/gleam/how-to/build-process.mdx index 83b8cb75..5e10a555 100644 --- a/apps/docs/content/gleam/how-to/build-process.mdx +++ b/apps/docs/content/gleam/how-to/build-process.mdx @@ -4,6 +4,7 @@ description: Learn more about Gleam' build process. --- import data from '@site/static/data.json'; +import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/gleam/how-to/deploy-process.mdx b/apps/docs/content/gleam/how-to/deploy-process.mdx index d29e8239..a8742d1a 100644 --- a/apps/docs/content/gleam/how-to/deploy-process.mdx +++ b/apps/docs/content/gleam/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Gleam Deploy process description: More about how Gleam deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/go/how-to/deploy-process.mdx b/apps/docs/content/go/how-to/deploy-process.mdx index 7c8fe098..12c6ceb1 100644 --- a/apps/docs/content/go/how-to/deploy-process.mdx +++ b/apps/docs/content/go/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Go Deploy process description: More about how go deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/java/how-to/deploy-process.mdx b/apps/docs/content/java/how-to/deploy-process.mdx index b83f40e4..8979c752 100644 --- a/apps/docs/content/java/how-to/deploy-process.mdx +++ b/apps/docs/content/java/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Java Deploy process description: More about how java deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/nginx/how-to/deploy-process.mdx b/apps/docs/content/nginx/how-to/deploy-process.mdx index 35a54cc9..a9097803 100644 --- a/apps/docs/content/nginx/how-to/deploy-process.mdx +++ b/apps/docs/content/nginx/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Nginx Deploy process description: More about how nginx deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/nodejs/how-to/build-process.mdx b/apps/docs/content/nodejs/how-to/build-process.mdx index 30585ec4..253d06f1 100644 --- a/apps/docs/content/nodejs/how-to/build-process.mdx +++ b/apps/docs/content/nodejs/how-to/build-process.mdx @@ -4,6 +4,7 @@ description: Learn more about node.js' build process. --- import data from '@site/static/data.json'; +import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/nodejs/how-to/deploy-process.mdx b/apps/docs/content/nodejs/how-to/deploy-process.mdx index 5f47d7c0..ee0d2962 100644 --- a/apps/docs/content/nodejs/how-to/deploy-process.mdx +++ b/apps/docs/content/nodejs/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Node.js Deploy process description: More about how node.js deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/php/how-to/deploy-process.mdx b/apps/docs/content/php/how-to/deploy-process.mdx index b14b317b..463f87ee 100644 --- a/apps/docs/content/php/how-to/deploy-process.mdx +++ b/apps/docs/content/php/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: PHP Deploy process description: More about how php deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/python/how-to/deploy-process.mdx b/apps/docs/content/python/how-to/deploy-process.mdx index e7d25f8d..265960af 100644 --- a/apps/docs/content/python/how-to/deploy-process.mdx +++ b/apps/docs/content/python/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Python Deploy process description: More about how python deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/rust/how-to/deploy-process.mdx b/apps/docs/content/rust/how-to/deploy-process.mdx index 70f33c87..899eb58b 100644 --- a/apps/docs/content/rust/how-to/deploy-process.mdx +++ b/apps/docs/content/rust/how-to/deploy-process.mdx @@ -3,12 +3,14 @@ title: Rust Deploy process description: More about how rust deploy process works on Zerops. --- +import Image from '/src/components/Image'; +

- image

From ed9341cbcd5baa5d53d3be7754dd3c26f7594616 Mon Sep 17 00:00:00 2001 From: Arjun Aditya Date: Sat, 15 Mar 2025 02:02:18 +0530 Subject: [PATCH 4/8] replace images --- apps/docs/content/bun/how-to/build-process.mdx | 10 +++++----- apps/docs/content/bun/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/bun/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/deno/how-to/build-process.mdx | 10 +++++----- apps/docs/content/deno/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/deno/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/elixir/how-to/build-process.mdx | 10 +++++----- .../docs/content/elixir/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/elixir/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/gleam/how-to/build-process.mdx | 10 +++++----- apps/docs/content/gleam/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/gleam/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/go/how-to/build-process.mdx | 10 +++++----- apps/docs/content/go/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/go/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/java/how-to/build-process.mdx | 10 +++++----- apps/docs/content/java/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/java/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/nginx/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/nginx/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/nodejs/how-to/build-process.mdx | 10 +++++----- .../docs/content/nodejs/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/nodejs/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/php/how-to/build-process.mdx | 10 +++++----- apps/docs/content/php/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/php/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/python/how-to/build-process.mdx | 10 +++++----- .../docs/content/python/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/python/how-to/deploy-process.mdx | 10 +++++----- apps/docs/content/rust/how-to/build-process.mdx | 10 +++++----- apps/docs/content/rust/how-to/customize-runtime.mdx | 12 +++++++----- apps/docs/content/rust/how-to/deploy-process.mdx | 10 +++++----- 32 files changed, 182 insertions(+), 160 deletions(-) diff --git a/apps/docs/content/bun/how-to/build-process.mdx b/apps/docs/content/bun/how-to/build-process.mdx index 004aeeb2..0c2b8e0e 100644 --- a/apps/docs/content/bun/how-to/build-process.mdx +++ b/apps/docs/content/bun/how-to/build-process.mdx @@ -7,11 +7,11 @@ import data from '@site/static/data.json'; import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/bun/how-to/customize-runtime.mdx b/apps/docs/content/bun/how-to/customize-runtime.mdx index fe0905f3..d045cd70 100644 --- a/apps/docs/content/bun/how-to/customize-runtime.mdx +++ b/apps/docs/content/bun/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customise Bun runtime environment description: Learn how you can customise your node.js runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/bun/how-to/deploy-process.mdx b/apps/docs/content/bun/how-to/deploy-process.mdx index 32ff39df..770c0a35 100644 --- a/apps/docs/content/bun/how-to/deploy-process.mdx +++ b/apps/docs/content/bun/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/deno/how-to/build-process.mdx b/apps/docs/content/deno/how-to/build-process.mdx index 20c50a05..29d499b1 100644 --- a/apps/docs/content/deno/how-to/build-process.mdx +++ b/apps/docs/content/deno/how-to/build-process.mdx @@ -7,11 +7,11 @@ import data from '@site/static/data.json'; import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/deno/how-to/customize-runtime.mdx b/apps/docs/content/deno/how-to/customize-runtime.mdx index b016f816..1b059a3c 100644 --- a/apps/docs/content/deno/how-to/customize-runtime.mdx +++ b/apps/docs/content/deno/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customise Deno runtime environment description: Learn how you can customise your deno runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/deno/how-to/deploy-process.mdx b/apps/docs/content/deno/how-to/deploy-process.mdx index da558b6d..7e980d49 100644 --- a/apps/docs/content/deno/how-to/deploy-process.mdx +++ b/apps/docs/content/deno/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/elixir/how-to/build-process.mdx b/apps/docs/content/elixir/how-to/build-process.mdx index dd799ae7..dd7d01b9 100644 --- a/apps/docs/content/elixir/how-to/build-process.mdx +++ b/apps/docs/content/elixir/how-to/build-process.mdx @@ -7,11 +7,11 @@ import data from '@site/static/data.json'; import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/elixir/how-to/customize-runtime.mdx b/apps/docs/content/elixir/how-to/customize-runtime.mdx index 822c3152..a3b90059 100644 --- a/apps/docs/content/elixir/how-to/customize-runtime.mdx +++ b/apps/docs/content/elixir/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customise Elixir runtime environment description: Learn how you can customise your Elixir runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/elixir/how-to/deploy-process.mdx b/apps/docs/content/elixir/how-to/deploy-process.mdx index 6f9b3871..48b985e6 100644 --- a/apps/docs/content/elixir/how-to/deploy-process.mdx +++ b/apps/docs/content/elixir/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/gleam/how-to/build-process.mdx b/apps/docs/content/gleam/how-to/build-process.mdx index 5e10a555..a2026581 100644 --- a/apps/docs/content/gleam/how-to/build-process.mdx +++ b/apps/docs/content/gleam/how-to/build-process.mdx @@ -7,11 +7,11 @@ import data from '@site/static/data.json'; import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/gleam/how-to/customize-runtime.mdx b/apps/docs/content/gleam/how-to/customize-runtime.mdx index dc46a23f..d9b7dd8f 100644 --- a/apps/docs/content/gleam/how-to/customize-runtime.mdx +++ b/apps/docs/content/gleam/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customise Gleam runtime environment description: Learn how you can customise your Gleam runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/gleam/how-to/deploy-process.mdx b/apps/docs/content/gleam/how-to/deploy-process.mdx index a8742d1a..c4297bf0 100644 --- a/apps/docs/content/gleam/how-to/deploy-process.mdx +++ b/apps/docs/content/gleam/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/go/how-to/build-process.mdx b/apps/docs/content/go/how-to/build-process.mdx index 40f6d9c0..5c4d8965 100644 --- a/apps/docs/content/go/how-to/build-process.mdx +++ b/apps/docs/content/go/how-to/build-process.mdx @@ -6,11 +6,11 @@ description: Learn more about go's build process. import data from '@site/static/data.json';

- image

diff --git a/apps/docs/content/go/how-to/customize-runtime.mdx b/apps/docs/content/go/how-to/customize-runtime.mdx index 5301b09a..851d3b96 100644 --- a/apps/docs/content/go/how-to/customize-runtime.mdx +++ b/apps/docs/content/go/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customize Go runtime environment description: Learn how you can customize your go runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/go/how-to/deploy-process.mdx b/apps/docs/content/go/how-to/deploy-process.mdx index 12c6ceb1..32d6b8cd 100644 --- a/apps/docs/content/go/how-to/deploy-process.mdx +++ b/apps/docs/content/go/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/java/how-to/build-process.mdx b/apps/docs/content/java/how-to/build-process.mdx index f1504625..daec78da 100644 --- a/apps/docs/content/java/how-to/build-process.mdx +++ b/apps/docs/content/java/how-to/build-process.mdx @@ -6,11 +6,11 @@ description: Learn more about java's build process. import data from '@site/static/data.json';

- image

diff --git a/apps/docs/content/java/how-to/customize-runtime.mdx b/apps/docs/content/java/how-to/customize-runtime.mdx index ce1dff95..a45c933b 100644 --- a/apps/docs/content/java/how-to/customize-runtime.mdx +++ b/apps/docs/content/java/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customize Java runtime environment description: Learn how you can customize your java runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/java/how-to/deploy-process.mdx b/apps/docs/content/java/how-to/deploy-process.mdx index 8979c752..6830254b 100644 --- a/apps/docs/content/java/how-to/deploy-process.mdx +++ b/apps/docs/content/java/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/nginx/how-to/customize-runtime.mdx b/apps/docs/content/nginx/how-to/customize-runtime.mdx index a5e1b502..688c1e86 100644 --- a/apps/docs/content/nginx/how-to/customize-runtime.mdx +++ b/apps/docs/content/nginx/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customize Nginx Static runtime environment description: Learn how you can customize your nginx static runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/nginx/how-to/deploy-process.mdx b/apps/docs/content/nginx/how-to/deploy-process.mdx index a9097803..45afd3af 100644 --- a/apps/docs/content/nginx/how-to/deploy-process.mdx +++ b/apps/docs/content/nginx/how-to/deploy-process.mdx @@ -84,11 +84,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/nodejs/how-to/build-process.mdx b/apps/docs/content/nodejs/how-to/build-process.mdx index 253d06f1..4c9d4cd2 100644 --- a/apps/docs/content/nodejs/how-to/build-process.mdx +++ b/apps/docs/content/nodejs/how-to/build-process.mdx @@ -7,11 +7,11 @@ import data from '@site/static/data.json'; import Image from '/src/components/Image';

- image

diff --git a/apps/docs/content/nodejs/how-to/customize-runtime.mdx b/apps/docs/content/nodejs/how-to/customize-runtime.mdx index 244ca7b1..3bb4c75d 100644 --- a/apps/docs/content/nodejs/how-to/customize-runtime.mdx +++ b/apps/docs/content/nodejs/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customize Node.js runtime environment description: Learn how you can customize your node.js runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/nodejs/how-to/deploy-process.mdx b/apps/docs/content/nodejs/how-to/deploy-process.mdx index ee0d2962..da38c477 100644 --- a/apps/docs/content/nodejs/how-to/deploy-process.mdx +++ b/apps/docs/content/nodejs/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/php/how-to/build-process.mdx b/apps/docs/content/php/how-to/build-process.mdx index 510b3e25..c15fab31 100644 --- a/apps/docs/content/php/how-to/build-process.mdx +++ b/apps/docs/content/php/how-to/build-process.mdx @@ -6,11 +6,11 @@ description: Learn more about php's build process. import data from '@site/static/data.json';

- image

diff --git a/apps/docs/content/php/how-to/customize-runtime.mdx b/apps/docs/content/php/how-to/customize-runtime.mdx index 02dc1595..90af2d4c 100644 --- a/apps/docs/content/php/how-to/customize-runtime.mdx +++ b/apps/docs/content/php/how-to/customize-runtime.mdx @@ -20,12 +20,14 @@ Additional packages and tools can be installed using [run.prepareCommands](/zero ## Runtime Flow +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/php/how-to/deploy-process.mdx b/apps/docs/content/php/how-to/deploy-process.mdx index 463f87ee..7a1ba2ac 100644 --- a/apps/docs/content/php/how-to/deploy-process.mdx +++ b/apps/docs/content/php/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/python/how-to/build-process.mdx b/apps/docs/content/python/how-to/build-process.mdx index df59e796..cf71c87e 100644 --- a/apps/docs/content/python/how-to/build-process.mdx +++ b/apps/docs/content/python/how-to/build-process.mdx @@ -6,11 +6,11 @@ description: Learn more about python's build process. import data from '@site/static/data.json';

- image

diff --git a/apps/docs/content/python/how-to/customize-runtime.mdx b/apps/docs/content/python/how-to/customize-runtime.mdx index a755a0d7..6b9700a1 100644 --- a/apps/docs/content/python/how-to/customize-runtime.mdx +++ b/apps/docs/content/python/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customize Python runtime environment description: Learn how you can customize your python runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/python/how-to/deploy-process.mdx b/apps/docs/content/python/how-to/deploy-process.mdx index 265960af..58529448 100644 --- a/apps/docs/content/python/how-to/deploy-process.mdx +++ b/apps/docs/content/python/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

diff --git a/apps/docs/content/rust/how-to/build-process.mdx b/apps/docs/content/rust/how-to/build-process.mdx index 4991cceb..3ddfa7e8 100644 --- a/apps/docs/content/rust/how-to/build-process.mdx +++ b/apps/docs/content/rust/how-to/build-process.mdx @@ -6,11 +6,11 @@ description: Learn more about rust's build process. import data from '@site/static/data.json';

- image

diff --git a/apps/docs/content/rust/how-to/customize-runtime.mdx b/apps/docs/content/rust/how-to/customize-runtime.mdx index 8bae3eb2..4a75638a 100644 --- a/apps/docs/content/rust/how-to/customize-runtime.mdx +++ b/apps/docs/content/rust/how-to/customize-runtime.mdx @@ -3,12 +3,14 @@ title: Customize Rust runtime environment description: Learn how you can customize your rust runtime environment on Zerops. --- +import Image from '/src/components/Image'; +

- image

diff --git a/apps/docs/content/rust/how-to/deploy-process.mdx b/apps/docs/content/rust/how-to/deploy-process.mdx index 899eb58b..85746400 100644 --- a/apps/docs/content/rust/how-to/deploy-process.mdx +++ b/apps/docs/content/rust/how-to/deploy-process.mdx @@ -86,11 +86,11 @@ Zerops keeps 10 last versions of your application in the internal storage. The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.

- image

From bbbe879749c815e5d465b7fb11def763169d7ee8 Mon Sep 17 00:00:00 2001 From: Arjun Aditya Date: Sat, 15 Mar 2025 02:45:56 +0530 Subject: [PATCH 5/8] use badges --- .../content/bun/how-to/build-pipeline.mdx | 69 +++++++++--------- .../content/deno/how-to/build-pipeline.mdx | 69 +++++++++--------- .../content/dotnet/how-to/build-pipeline.mdx | 69 +++++++++--------- .../content/elixir/how-to/build-pipeline.mdx | 69 +++++++++--------- .../content/gleam/how-to/build-pipeline.mdx | 69 +++++++++--------- .../docs/content/go/how-to/build-pipeline.mdx | 69 +++++++++--------- .../content/java/how-to/build-pipeline.mdx | 69 +++++++++--------- .../content/nginx/how-to/build-pipeline.mdx | 41 ++++++----- .../content/php/how-to/build-pipeline.mdx | 73 ++++++++++--------- .../content/python/how-to/build-pipeline.mdx | 65 +++++++++-------- .../content/rust/how-to/build-pipeline.mdx | 69 +++++++++--------- 11 files changed, 371 insertions(+), 360 deletions(-) diff --git a/apps/docs/content/bun/how-to/build-pipeline.mdx b/apps/docs/content/bun/how-to/build-pipeline.mdx index deacb492..45c29e10 100644 --- a/apps/docs/content/bun/how-to/build-pipeline.mdx +++ b/apps/docs/content/bun/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Bun build & deploy pipeline description: Learn more about how you can configure your node.js service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -97,9 +98,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for Bun builds: @@ -151,9 +152,9 @@ To customise your build environment use the [prepareCommands](bun/how-to/build-p Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -175,9 +176,9 @@ The os version is fixed and cannot be customised. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the build environment by installing additional dependencies or tools to the base build environment. +Customises the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -225,9 +226,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -286,9 +287,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -389,9 +390,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -405,9 +406,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -433,9 +434,9 @@ Read more about [environment variables](bun/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Bun version for your runtime. Following options are available for Bun runtimes: @@ -494,9 +495,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customise your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -514,9 +515,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -530,9 +531,9 @@ Each port has following attributes: | protocol | **Optional.** Defines the protocol. Allowed values are `TCP` or `UDP`. Default value is `TCP`. | | httpSupport | **Optional.** `httpSupport = true` is the default setting for TCP protocol. Set `httpSupport = false` if a web server isn't running on the port. Zerops uses this information for the configuration of [public access](/features/access). `httpSupport = true` is available only in combination with the TCP protocol. | -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the Bun runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the Bun runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Bun environment contains {data.alpine.default} the selected @@ -615,9 +616,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -653,9 +654,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -676,9 +677,9 @@ zerops: Read more about [environment variables](bun/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your Bun application. +Defines the start command for your Bun application. ```yml zerops: @@ -695,9 +696,9 @@ zerops: We recommend starting your Bun application using `bun start`. -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -772,9 +773,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -796,9 +797,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](bun/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](bun/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/deno/how-to/build-pipeline.mdx b/apps/docs/content/deno/how-to/build-pipeline.mdx index eefb5e51..edfbfeda 100644 --- a/apps/docs/content/deno/how-to/build-pipeline.mdx +++ b/apps/docs/content/deno/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Deno build & deploy pipeline description: Learn more about how you can configure your deno service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -94,9 +95,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for Deno builds: @@ -146,9 +147,9 @@ To customise your build environment use the [prepareCommands](/deno/how-to/build Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -170,9 +171,9 @@ The os version is fixed and cannot be customised. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the build environment by installing additional dependencies or tools to the base build environment. +Customises the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -220,9 +221,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -279,9 +280,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -382,9 +383,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -398,9 +399,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -426,9 +427,9 @@ Read more about [environment variables](/deno/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Deno version for your runtime. Following options are available for Deno builds: @@ -487,9 +488,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customise your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -507,9 +508,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -523,9 +524,9 @@ Each port has following attributes: | protocol | **Optional.** Defines the protocol. Allowed values are `TCP` or `UDP`. Default value is `TCP`. | | httpSupport | **Optional.** `httpSupport = true` is the default setting for TCP protocol. Set `httpSupport = false` if a web server isn't running on the port. Zerops uses this information for the configuration of [public access](/features/access). `httpSupport = true` is available only in combination with the TCP protocol. | -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the Deno runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the Deno runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Deno environment contains {data.alpine.default} the selected @@ -608,9 +609,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -646,9 +647,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -669,9 +670,9 @@ zerops: Read more about [environment variables](/deno/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your Deno application. +Defines the start command for your Deno application. ```yml zerops: @@ -688,9 +689,9 @@ zerops: We recommend starting your Deno application using `deno task start`. -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -765,9 +766,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -789,9 +790,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/deno/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/deno/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/dotnet/how-to/build-pipeline.mdx b/apps/docs/content/dotnet/how-to/build-pipeline.mdx index bc76b852..8e6151c1 100644 --- a/apps/docs/content/dotnet/how-to/build-pipeline.mdx +++ b/apps/docs/content/dotnet/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your .NET build & deploy pipeline description: Learn more about how you can configure your dotnet service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -98,9 +99,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for .NET builds: @@ -150,9 +151,9 @@ To customize your build environment use the [prepareCommands](/dotnet/how-to/bui Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -174,9 +175,9 @@ The os version is fixed and cannot be customized. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customizes the build environment by installing additional dependencies or tools to the base build environment. +Customizes the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -224,9 +225,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -283,9 +284,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -384,9 +385,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -400,9 +401,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -428,9 +429,9 @@ Read more about [environment variables](/dotnet/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current .NET version for your runtime. Following options are available for .NET builds: @@ -489,9 +490,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customise your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -509,9 +510,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -543,9 +544,9 @@ Each port has following attributes: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the .NET runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the .NET runtime environment by installing additional dependencies or tools to the runtime base environment.

The base .NET environment contains {data.alpine.default}, the selected @@ -630,9 +631,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -668,9 +669,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -691,9 +692,9 @@ zerops: Read more about [environment variables](/dotnet/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your .NET application. +Defines the start command for your .NET application. ```yml zerops: @@ -708,9 +709,9 @@ zerops: start: cd app && dotnet dnet.dll ``` -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -800,9 +801,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -824,9 +825,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/dotnet/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/dotnet/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/elixir/how-to/build-pipeline.mdx b/apps/docs/content/elixir/how-to/build-pipeline.mdx index adf89714..caf59615 100644 --- a/apps/docs/content/elixir/how-to/build-pipeline.mdx +++ b/apps/docs/content/elixir/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Elixir build & deploy pipeline description: Learn more about how you can configure your Elixir service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -95,9 +96,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for Elixir builds: @@ -147,9 +148,9 @@ To customise your build environment use the [prepareCommands](/elixir/how-to/bui Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -171,9 +172,9 @@ The os version is fixed and cannot be customised. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the build environment by installing additional dependencies or tools to the base build environment. +Customises the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -221,9 +222,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -282,9 +283,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -385,9 +386,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -401,9 +402,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -429,9 +430,9 @@ Read more about [environment variables](/elixir/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Elixir version for your runtime. Following options are available for Elixir builds: @@ -490,9 +491,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customise your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -510,9 +511,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -526,9 +527,9 @@ Each port has following attributes: | protocol | **Optional.** Defines the protocol. Allowed values are `TCP` or `UDP`. Default value is `TCP`. | | httpSupport | **Optional.** `httpSupport = true` is the default setting for TCP protocol. Set `httpSupport = false` if a web server isn't running on the port. Zerops uses this information for the configuration of [public access](/features/access). `httpSupport = true` is available only in combination with the TCP protocol. | -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the Elixir runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the Elixir runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Elixir environment contains {data.alpine.default} the selected @@ -611,9 +612,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -649,9 +650,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -672,9 +673,9 @@ zerops: Read more about [environment variables](/elixir/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your Elixir application. +Defines the start command for your Elixir application. ```yml zerops: @@ -691,9 +692,9 @@ zerops: We recommend starting your Elixir application using `npm start`. -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -768,9 +769,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -792,9 +793,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/elixir/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/elixir/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/gleam/how-to/build-pipeline.mdx b/apps/docs/content/gleam/how-to/build-pipeline.mdx index 7d3862cb..d03c3422 100644 --- a/apps/docs/content/gleam/how-to/build-pipeline.mdx +++ b/apps/docs/content/gleam/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Gleam build & deploy pipeline description: Learn more about how you can configure your Gleam service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -96,9 +97,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for Gleam builds: @@ -148,9 +149,9 @@ To customise your build environment use the [prepareCommands](/gleam/how-to/buil Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -172,9 +173,9 @@ The os version is fixed and cannot be customised. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the build environment by installing additional dependencies or tools to the base build environment. +Customises the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -222,9 +223,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -283,9 +284,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -386,9 +387,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -402,9 +403,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -430,9 +431,9 @@ Read more about [environment variables](/gleam/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Gleam version for your runtime. Following options are available for Gleam runtimes: @@ -491,9 +492,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customise your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -511,9 +512,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -527,9 +528,9 @@ Each port has following attributes: | protocol | **Optional.** Defines the protocol. Allowed values are `TCP` or `UDP`. Default value is `TCP`. | | httpSupport | **Optional.** `httpSupport = true` is the default setting for TCP protocol. Set `httpSupport = false` if a web server isn't running on the port. Zerops uses this information for the configuration of [public access](/features/access). `httpSupport = true` is available only in combination with the TCP protocol. | -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the Gleam runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the Gleam runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Gleam environment contains {data.alpine.default} the selected @@ -612,9 +613,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -650,9 +651,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -673,9 +674,9 @@ zerops: Read more about [environment variables](/gleam/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your Gleam application. +Defines the start command for your Gleam application. ```yml zerops: @@ -692,9 +693,9 @@ zerops: We recommend starting your Gleam application using `npm start`. -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -769,9 +770,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -793,9 +794,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/gleam/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/gleam/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/go/how-to/build-pipeline.mdx b/apps/docs/content/go/how-to/build-pipeline.mdx index cb1bb187..66d62f83 100644 --- a/apps/docs/content/go/how-to/build-pipeline.mdx +++ b/apps/docs/content/go/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Go build & deploy pipeline description: Learn more about how you can configure your go application's build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -92,9 +93,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for Go builds: @@ -144,9 +145,9 @@ To customize your build environment use the [prepareCommands](/go/how-to/build-p Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -168,9 +169,9 @@ The os version is fixed and cannot be customized. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customizes the build environment by installing additional dependencies or tools to the base build environment. +Customizes the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -218,9 +219,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -277,9 +278,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -378,9 +379,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -394,9 +395,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -422,9 +423,9 @@ Read more about [environment variables](/go/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Go version for your runtime. Following options are available for Go builds: @@ -483,9 +484,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customise your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -503,9 +504,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -538,9 +539,9 @@ Each port has following attributes: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the Go runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the Go runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Go environment contains {data.alpine.default}, the selected @@ -622,9 +623,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -660,9 +661,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -683,9 +684,9 @@ zerops: Read more about [environment variables](/go/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your Go application. +Defines the start command for your Go application. ```yml zerops: @@ -702,9 +703,9 @@ zerops: We recommend starting your Go application using `./app`. -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -795,9 +796,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -819,9 +820,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/go/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/go/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/java/how-to/build-pipeline.mdx b/apps/docs/content/java/how-to/build-pipeline.mdx index 8c39654d..2cc3c4b2 100644 --- a/apps/docs/content/java/how-to/build-pipeline.mdx +++ b/apps/docs/content/java/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Java build & deploy pipeline description: Learn more about how you can configure your java service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; @@ -91,9 +92,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for Java builds: @@ -144,9 +145,9 @@ To customize your build environment use the [prepareCommands](/java/how-to/build Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -168,9 +169,9 @@ The os version is fixed and cannot be customized. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customizes the build environment by installing additional dependencies or tools to the base build environment. +Customizes the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -218,9 +219,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -277,9 +278,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -378,9 +379,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -394,9 +395,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -421,9 +422,9 @@ Read more about [environment variables](/java/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Java version for your runtime. Following options are available for Java builds: @@ -482,9 +483,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customize your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -502,9 +503,9 @@ We are currently using following os version: The os version is fixed and cannot be customized. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -537,9 +538,9 @@ Each port has following attributes: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customizes the Java runtime environment by installing additional dependencies or tools to the runtime base environment. +Customizes the Java runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Java environment contains {data.alpine.default}, the selected major @@ -623,9 +624,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -661,9 +662,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -683,9 +684,9 @@ zerops: Read more about [environment variables](/java/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your Java application. +Defines the start command for your Java application. ```yml zerops: @@ -702,9 +703,9 @@ zerops: We recommend starting your Java application using `java -jar target/app.jar`. -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -794,9 +795,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -818,9 +819,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/java/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/java/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/nginx/how-to/build-pipeline.mdx b/apps/docs/content/nginx/how-to/build-pipeline.mdx index 5cfce5ca..a786bb59 100644 --- a/apps/docs/content/nginx/how-to/build-pipeline.mdx +++ b/apps/docs/content/nginx/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Nginx build & deploy pipeline description: Learn more about how you can configure your nginx service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -114,9 +115,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Nginx version for your runtime. Following options are available for Nginx builds: @@ -175,9 +176,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customize your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -195,9 +196,9 @@ We are currently using following os version: The os version is fixed and cannot be customized. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. :::info If no ports are specified, Zerops adds the port TCP 80 automatically. @@ -240,9 +241,9 @@ Each port has following attributes: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customizes the Nginx runtime environment by installing additional dependencies or tools to the runtime base environment. +Customizes the Nginx runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Nginx environment contains {data.alpine.default}, the selected @@ -332,9 +333,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -370,9 +371,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. -### documentRoot +### documentRoot -_OPTIONAL._ Customizes the folder that will be used as the root of the publicly accessible web server content. +Customizes the folder that will be used as the root of the publicly accessible web server content. :::info By default, the document root is configured to `/var/www`. @@ -395,9 +396,9 @@ zerops: documentRoot: public ``` -### siteConfigPath +### siteConfigPath -_OPTIONAL._ Sets the custom Nginx configuration. +Sets the custom Nginx configuration. :::info If you don't set your custom configuration Zerops applies the [default](/nginx/how-to/customize-web-server#default-nginx-configuration) configuration. @@ -406,9 +407,9 @@ If you don't set your custom configuration Zerops applies the [default](/nginx/h The file must be deployed in the runtime container. Enter the path to the file relative to the `/var/www` folder. Read more about the [web server customization](/nginx/how-to/customize-web-server). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -428,9 +429,9 @@ zerops: Read more about [environment variables](/nginx/how-to/env-variables) in Zerops. -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -524,9 +525,9 @@ Read more about how the [health check works] in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/nginx/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/nginx/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/php/how-to/build-pipeline.mdx b/apps/docs/content/php/how-to/build-pipeline.mdx index 86aad20a..d22069ed 100644 --- a/apps/docs/content/php/how-to/build-pipeline.mdx +++ b/apps/docs/content/php/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your PHP build & deploy pipeline description: Learn more about how you can configure your php service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -95,9 +96,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for PHP builds: @@ -147,9 +148,9 @@ To customise your build environment use the [prepareCommands](/php/how-to/build- Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -171,9 +172,9 @@ The os version is fixed and cannot be customised. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the build environment by installing additional dependencies or tools to the base build environment. +Customises the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -221,9 +222,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -280,9 +281,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -382,9 +383,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -398,9 +399,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -426,9 +427,9 @@ Read more about [environment variables](/php/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current PHP version for your runtime. Following options are available for PHP builds: @@ -488,9 +489,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customise your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -508,9 +509,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. :::info If no ports are specified, Zerops adds the port TCP 80 automatically. @@ -553,9 +554,9 @@ Each port has following attributes: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the PHP runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the PHP runtime environment by installing additional dependencies or tools to the runtime base environment.

The base PHP environment contains {data.alpine.default}, the selected @@ -645,9 +646,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -683,9 +684,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### documentRoot +### documentRoot -_OPTIONAL._ Customizes the folder that will be used as the root of the publicly accessible web server content. +Customizes the folder that will be used as the root of the publicly accessible web server content. :::info By default, the document root is configured to `/var/www`. @@ -708,9 +709,9 @@ zerops: documentRoot: public ``` -### siteConfigPath +### siteConfigPath -_OPTIONAL._ Sets the custom Nginx or Apache configuration. +Sets the custom Nginx or Apache configuration. :::info By default, the default [nginx](/php/how-to/customize-web-server#default-nginx-configuration) or [Apache](/php/how-to/customize-web-server#default-apache-configuration) web server configuration is set. @@ -719,9 +720,9 @@ By default, the default [nginx](/php/how-to/customize-web-server#default-nginx-c The file must be deployed in the runtime container. Enter the path to the file relative to the `/var/www` folder. Read more about the [web server customization](/php/how-to/customize-web-server). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -742,9 +743,9 @@ zerops: Read more about [environment variables](/php/how-to/env-variables) in Zerops. -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -836,9 +837,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -860,9 +861,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/php/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/php/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/python/how-to/build-pipeline.mdx b/apps/docs/content/python/how-to/build-pipeline.mdx index f29a9539..d5c7579b 100644 --- a/apps/docs/content/python/how-to/build-pipeline.mdx +++ b/apps/docs/content/python/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Python build & deploy pipeline description: Learn more about how you can configure your python service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -93,9 +94,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for Python builds: @@ -145,9 +146,9 @@ To customize your build environment use the [prepareCommands](/python/how-to/bui Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -169,9 +170,9 @@ The os version is fixed and cannot be customized. Changing the OS setting will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache behavior. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customizes the build environment by installing additional dependencies or tools to the base build environment. +Customizes the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -235,9 +236,9 @@ prepareCommands: - apt install python3-pip # already installed for Python services ``` -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -336,9 +337,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -352,9 +353,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -380,9 +381,9 @@ Read more about [environment variables](/python/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Python version for your runtime. Following options are available for Python builds: @@ -441,9 +442,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customize your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -461,9 +462,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -494,9 +495,9 @@ Each port has following attributes: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the Python runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the Python runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Python environment contains {data.alpine.default}, the selected @@ -578,9 +579,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -616,9 +617,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build:prepareCommands](#preparecommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -639,9 +640,9 @@ zerops: Read more about [environment variables](/python/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your Python application. +Defines the start command for your Python application. ```yml zerops: @@ -656,9 +657,9 @@ zerops: start: app.py ``` -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -750,9 +751,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -774,9 +775,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/python/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/python/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. diff --git a/apps/docs/content/rust/how-to/build-pipeline.mdx b/apps/docs/content/rust/how-to/build-pipeline.mdx index a25369f8..c523f5e5 100644 --- a/apps/docs/content/rust/how-to/build-pipeline.mdx +++ b/apps/docs/content/rust/how-to/build-pipeline.mdx @@ -3,6 +3,7 @@ title: Configure Your Rust build & deploy pipeline description: Learn more about how you can configure your rust service for build & deploy pipeline. --- +import Badge from 'docs/src/components/Badge'; import data from '@site/static/data.json'; import UnorderedCodeList from 'docs/src/components/UnorderedCodeList'; @@ -94,9 +95,9 @@ Each service configuration contains at least two sections: **build** and **run** ## Build pipeline configuration -### base +### base -_REQUIRED._ Sets the base technology for the build environment. +Sets the base technology for the build environment. Following options are available for Rust builds: @@ -146,9 +147,9 @@ To customize your build environment use the [prepareCommands](/rust/how-to/build Modifying the base technology will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### os +### os -_OPTIONAL._ Sets the operating system for the build environment. +Sets the operating system for the build environment. Following options are available: @@ -170,9 +171,9 @@ The os version is fixed and cannot be customized. Modifying the OS will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for more details about cache invalidation. ::: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customizes the build environment by installing additional dependencies or tools to the base build environment. +Customizes the build environment by installing additional dependencies or tools to the base build environment. The base build environment contains: @@ -219,9 +220,9 @@ If any command fails, it returns an exit code other than 0 and the build is canc You can configure your prepare commands to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### buildCommands +### buildCommands -_REQUIRED._ Defines build commands. +Defines build commands. ```yml zerops: @@ -276,9 +277,9 @@ buildCommands: If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `buildCommands` are finished, the application build is completed and ready for the deploy phase. -### deployFiles +### deployFiles -_REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. +Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use `.deployignore` file. ```yml # REQUIRED. Select which files / folders to deploy after @@ -376,9 +377,9 @@ This example above ignores `file.txt` in ANY directory named `src`, such as: `.deployignore` file also works with `zcli service deploy` command. ::: -### cache +### cache -_OPTIONAL._ Defines which files or folders will be cached for the next build. +Defines which files or folders will be cached for the next build. ```yml # OPTIONAL. Which files / folders you want to cache for the next build. @@ -392,9 +393,9 @@ The cache attribute supports the [~ wildcard character](#how-to-use-a-wildcard-i Learn more about the [build cache system](/features/build-cache) in Zerops. -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the build environment. +Defines the environment variables for the build environment. Enter one or more env variables in following format: @@ -420,9 +421,9 @@ Read more about [environment variables](/rust/how-to/env-variables) in Zerops. ## Runtime configuration -### base +### base -_OPTIONAL._ Sets the base technology for the runtime environment. +Sets the base technology for the runtime environment. If you don't specify the `run.base` attribute, Zerops keeps the current Rust version for your runtime. Following options are available for Rust builds: @@ -482,9 +483,9 @@ See the full list of supported [run base environments](/zerops-yml/base-list). To customize your build environment use the `prepareCommands` attribute. -### os +### os -_OPTIONAL._ Sets the operating system for the runtime environment. +Sets the operating system for the runtime environment. Following options are available: @@ -502,9 +503,9 @@ We are currently using following os version: The os version is fixed and cannot be customised. ::: -### ports +### ports -_OPTIONAL._ Specifies one or more internal ports on which your application will listen. +Specifies one or more internal ports on which your application will listen. Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a **dedicated private network**. To connect to a service within the same project, just use the service hostname and its internal port. @@ -537,9 +538,9 @@ Each port has following attributes: -### prepareCommands +### prepareCommands -_OPTIONAL._ Customises the Rust runtime environment by installing additional dependencies or tools to the runtime base environment. +Customises the Rust runtime environment by installing additional dependencies or tools to the runtime base environment.

The base Rust environment contains {data.alpine.default}, the selected @@ -629,9 +630,9 @@ zerops: In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered. -### initCommands +### initCommands -_OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted. +Defines one or more commands to be run each time a new runtime container is started or a container is restarted. ```yml zerops: @@ -667,9 +668,9 @@ If any of the `initCommands` fails, it returns an exit code other than 0, but de You can configure your `initCommands` to be run in a single shell instance or multiple shell instances. The format is identical to [build commands](#buildcommands). -### envVariables +### envVariables -_OPTIONAL._ Defines the environment variables for the runtime environment. +Defines the environment variables for the runtime environment. Enter one or more env variables in following format: @@ -690,9 +691,9 @@ zerops: Read more about [environment variables](/rust/how-to/env-variables) in Zerops. -### start +### start -_REQUIRED._ Defines the start command for your Rust application. +Defines the start command for your Rust application. ```yml zerops: @@ -707,9 +708,9 @@ zerops: start: ./app ``` -### health check +### healthCheck -_OPTIONAL._ Defines a health check. +Defines a health check. `healthCheck` requires either one `httpGet` object or one `exec` object. @@ -801,9 +802,9 @@ zerops: Read more about how the [health check works] in Zerops. -### crontab +### crontab -_OPTIONAL._ Defines cron jobs. +Defines cron jobs. Setup cron jobs in the following format: @@ -825,9 +826,9 @@ Read more about setting up [cron](/references/cron) in Zerops. ## Deploy configuration -### readiness check +### readinessCheck -_OPTIONAL._ Defines a readiness check. Read more about how the [readiness check works](/rust/how-to/deploy-process#readiness-checks) in Zerops. +Defines a readiness check. Read more about how the [readiness check works](/rust/how-to/deploy-process#readiness-checks) in Zerops. `readinessCheck` requires either one `httpGet` object or one `exec` object. From 312ab233163094216847cceafe604e565365bdc2 Mon Sep 17 00:00:00 2001 From: Arjun Aditya Date: Sat, 15 Mar 2025 17:44:28 +0530 Subject: [PATCH 6/8] Update cron.mdx --- apps/docs/content/zerops-yml/cron.mdx | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/apps/docs/content/zerops-yml/cron.mdx b/apps/docs/content/zerops-yml/cron.mdx index 2dfcc751..65dfeeea 100644 --- a/apps/docs/content/zerops-yml/cron.mdx +++ b/apps/docs/content/zerops-yml/cron.mdx @@ -3,19 +3,19 @@ title: Cron Jobs & Tasks description: Learn how to set up automated tasks and scheduled jobs in Zerops --- +import Badge from 'docs/src/components/Badge'; + Cron jobs are scheduled commands that execute automatically inside a service's containers based on defined timing rules. In Zerops, these jobs are configured in the `run` section of `zerops.yml` file under the `crontab` key. ## Parameters -### command -*string, REQUIRED* +### command The shell command to execute at the scheduled time. This can be any valid command. -### timing -*string, REQUIRED* +### timing The schedule for when the task should run, specified in standard cron format using five space-separated fields: - Minute (0–59) @@ -28,15 +28,13 @@ The schedule for when the task should run, specified in standard cron format usi - `"0 5 * * *"` – Runs daily at 5:00 AM. - `"*/10 * * * *"` – Runs every 10 minutes. -### allContainers -*boolean, REQUIRED* +### allContainers **Options:** - `true` – Command runs on all containers. - `false` – Command runs on only one container. -### workingDir -*string, REQUIRED* +### workingDir Specifies the directory where the command will be executed. If not set, it defaults to `/var/www`. From 192c54476b391a60e7db63803296fb9c45b874f8 Mon Sep 17 00:00:00 2001 From: Arjun Aditya Date: Sat, 15 Mar 2025 18:05:26 +0530 Subject: [PATCH 7/8] Update faq.mdx --- apps/docs/content/help/faq.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/apps/docs/content/help/faq.mdx b/apps/docs/content/help/faq.mdx index 78d519cc..4a218b10 100644 --- a/apps/docs/content/help/faq.mdx +++ b/apps/docs/content/help/faq.mdx @@ -16,8 +16,7 @@ Get quick answers to your related questions about Zerops from frequently asked q You can access the Zerops Dashboard GUI directly at app.zerops.io. - It's free to get started, and no credit card is required! However, we - recommend visiting our pricing page to explore the options that best suit your needs. + You get $15 free credit to get started. No credit card is required! However, we recommend using our [pricing calculator](/features/pricing#pricing-calculator) to calculate your monthly costs. Navigate to the main menu in the Zerops GUI (with your icon) and add a new user with the selected email to your team. @@ -32,4 +31,7 @@ Get quick answers to your related questions about Zerops from frequently asked q You can reach us on our Discord server for support. For additional contact options, please visit our contacts page. + + You can reach us on our Discord server for support. For additional contact options, please visit our contacts page. + From bc6e24255903c392c5712c2e5ccb0ccab9b66926 Mon Sep 17 00:00:00 2001 From: Arjun Aditya Date: Sat, 15 Mar 2025 18:25:17 +0530 Subject: [PATCH 8/8] fix imports --- apps/docs/content/go/how-to/build-process.mdx | 1 + apps/docs/content/java/how-to/build-process.mdx | 1 + apps/docs/content/php/how-to/build-process.mdx | 1 + apps/docs/content/python/how-to/build-process.mdx | 1 + apps/docs/content/rust/how-to/build-process.mdx | 1 + 5 files changed, 5 insertions(+) diff --git a/apps/docs/content/go/how-to/build-process.mdx b/apps/docs/content/go/how-to/build-process.mdx index 5c4d8965..910c581d 100644 --- a/apps/docs/content/go/how-to/build-process.mdx +++ b/apps/docs/content/go/how-to/build-process.mdx @@ -4,6 +4,7 @@ description: Learn more about go's build process. --- import data from '@site/static/data.json'; +import Image from '/src/components/Image';