source template

starting source

Templates include built-in sources from external storage and sources distributed by the editor. It's a snapshot. The template itself creates DB, release, web processes, logs and backups. It doesn't.

• Users see live screen previews and sample data from the list of templates.
• The internal default template is only used to create a blank website; in public lists and MCPs, Doesn't display.
• The editor distribution displays the responsible icon when there is no thumbnail.
• Preview prepares a temporary UI server only when opened and automatically terminates when unused.
• When no Preview build exists, a spinner remains visible instead of a blank white screen until the automatic build is ready.
• Importing a template creates an independent website. If the source has DB models, its shared database is created by the first build that needs it.
• The editor distribution includes only sample JSON in app/preview, the operational DB, Secret, files uploads and build output are not included.

Template Management

• The user website is web-{12 digits} in TEMPLATE_ROOT, and the template is in the same location. Separate into tmp-{12 digits} folders.
• The basic skeleton, metadata, thumbnails, and app, public, server, and shared sources are Keep them all in each tmp-* folder.
• Language-specific templates keep lang as ko in ko/package.json and en in en/package.json; never copy one language setting into the other.
• When uploading a thumbnail, convert it to JPEG and save it in .cake/thumbnail.jpg. Lists and MCP also only use JPEG files.
• The priority of each .cake/template.json is the template display order. Lower numbers are displayed first, and existing templates without values ​​are treated as 1000.
• tmp-000000000000 is the internal startup source for your new website and is listed in the template list. Excluded.
• app/preview stores Preview JSON generated from the rows currently returned by each model seed. Cake20 creates the folder as needed and preserves the path through template cloning and ZIP export or import.
• Templates are not included in the management project Git, so when the runtime version is changed You can modify the tmp-* source of external storage at once.
• Administrators can use templates on the right side of the resolution menu at the top of the editor preview. You can press Deploy to add the current test source as a new template.
• Template preview reads the package.json device and orientation from the deployment source. Displays the main target device frame and orientation.
• The Manager checks the Preview cache of public templates after startup and every hour. Generates only missing builds sequentially. Administrators can use the Templates tab in Administrator Settings. You can turn this feature off.
• The distribution is stored atomically in TEMPLATE_ROOT/tmp-{12 digits} and is stored on the website. Equivalent to Git Leave a checkpoint at the viewpoint.
• Selecting a template creates a regular website. Its shared database is created when source with DB models is built for the first time.

Order of use

• Check the actual screen with a preview from the template list and select a starting source.
• Enter a display name and it will be copied to your independent website.
• When using it as is, start right from the website list and only make modifications when necessary. I use an editor and a reviewer.
• When the administrator reuses it as a starting source, check the distribution at the top of the editor. Click Deploy Template from the right-side drop-down menu.