Skip to main content
Ghost is an open-source publishing platform for blogs, newsletters, and membership sites. You write and manage everything from the Ghost admin panel; the public site is served at your *.suji.fr address. This guide covers configuring Ghost on Suji. Check the version and release notes shown in the marketplace before installing or upgrading. Ghost is maintained upstream; Suji provides the marketplace packaging.

​
Before you install

Nothing to prepare. You’ll create your admin (owner) account in the browser on first run. If you later want to send newsletters or member emails, you’ll add an email provider — see Email & newsletters.
Ghost has no generated password and no credentials file — the first person to open the admin URL creates the owner account. Set yours up immediately after install (see below).

​
Install

Dashboard → Apps → Ghost → Install: A Small VPS is a starting point for a small publication with spare capacity. The template limits the Ghost container to 1 GiB; larger workloads need their own sizing checks. See Recommended size. Click Deploy. Follow deployment progress until the install is running. Startup time varies with image downloads, initialization and VM capacity. Your site is then live at https://ghost-<random>.suji.fr, served over HTTPS through the tunnel.

​
First connection — create your owner account

  1. Open the admin panel at https://ghost-<random>.suji.fr/ghost (the /ghost path).
  2. Ghost shows a Create your account screen on first run.
  3. Enter your site title, name, email, and a password. This is the owner account.
  4. You land in the Ghost admin.
The admin URL is public the moment the install is running. Until you complete setup, anyone who reaches /ghost can claim the owner account. Do it right after deploy.
On later visits, /ghost shows a normal sign-in. The public site lives at the root (/).

​
Writing & publishing

Inside the Ghost admin:
  • Posts / Pages — write in the editor, then Publish.
  • Design / Branding — set your theme, colors, logo; upload custom themes under Settings → Design.
  • Members — enable signups/subscriptions under Settings → Membership (email setup required to actually send to members — see below).
Open the public site to verify each published change; caches can delay what visitors see.

​
Email & newsletters

The install ships with no email provider configured, so member signup confirmations, password resets, staff invites, and newsletters won’t send until you add one.
  • Transactional email (invites, password resets) needs a mail transport supported by Ghost. Configure SMTP using your provider’s documented settings and test delivery; port 587 with STARTTLS is a common option.
  • Bulk newsletters use Ghost’s Mailgun integration. Configure it in Ghost Admin using the upstream email settings.
For transactional mail, add the supported mail__* variables in Variables and click Apply changes. Configure newsletter delivery separately in Ghost Admin.

​
Custom domain

Ghost uses its configured Site URL for links and feeds. The template receives Suji’s public URL automatically. To use your own hostname, follow Custom domains, then verify Ghost’s URL, links, images and sign-in after activation. Update any external integrations that depend on the old hostname.

​
Day-to-day management

​
Troubleshooting

The admin is at the /ghost path, not the site root. The “Forgot?” link needs email configured (see Email & newsletters) — so set email up before you need a reset. Without email, recovering a locked-out owner means resetting it directly in Ghost’s database via the Terminal.
Expected until you configure an email provider. Check the transactional SMTP settings and delivery logs; bulk newsletters need the separate Mailgun configuration. See Email & newsletters.
Ghost isn’t reachable through the tunnel yet — usually still starting (wait ~30 s, especially after an upgrade). If it persists, the Logs tab shows why the container isn’t up.

​
Where things live

This template runs Ghost on SQLite, with no separate database container. Site data lives in ghost-content. Ghost’s official production stack uses MySQL; the SQLite template is not that upstream-supported production configuration. Assess that difference before using it for a production publication. The template also disables staff device-verification emails because no SMTP service is configured; review this setting after setting up mail.
Uninstalling deletes the volume by default — that’s your whole site (posts, members, images, theme). Choose keep data during uninstall if you want to preserve it.
  • Start with Small for a small site with spare capacity. The template declares 512 MiB minimum and 1 GiB recommended memory, with a 1 GiB container limit; these are packaging estimates, not a capacity guarantee.
  • Disk is the thing to watch on an image-heavy site — uploads accumulate in the content volume. Size storage accordingly.
  • If you run other apps on the same VM, remember the VM’s total CPU/memory is shared.

​
Reporting issues