Domains & Storefront Hosting
Each store gets a domain where customers can access it. You can use an auto-assigned subdomain or connect your own custom domain.
Auto-Assigned Domains
When you create a store from a template, the system automatically assigns a subdomain:
my-store.entaprenua.com
The subdomain is derived from your store's slug. If the slug is already taken, a random suffix is appended (e.g., my-store-a3f2.entaprenua.com).
Auto-assigned domains are available immediately after store creation.
Custom Domains
To use your own domain (e.g., shop.mystore.com):
- Go to Admin → Settings → General
- Set the Domain Name field to your custom domain
- Configure DNS:
Type: CNAME
Name: shop (or @ for root domain)
Value: entaprenua.com
TTL: 3600
- Wait for DNS propagation (usually a few minutes, up to 48 hours)
Once configured, your storefront is accessible at your custom domain. The auto-assigned subdomain continues to work as a fallback.
How Routing Works
Entaprenua's proxy router uses Redis to map domains to store processes:
- A request arrives at
my-store.entaprenua.com - The router looks up the domain in Redis
- It finds the store's port (e.g.,
store-st_xxxx → localhost:3001) - The request is proxied to the store's Node.js process
- The storefront handles the request and returns the response
This means every store gets its own process, its own port, and complete isolation from other stores.
Starting and Stopping
After a deployment, the storefront auto-starts. You can manually control it:
- Start: Launches the process on the store's port
- Stop: Gracefully terminates the process
- Redeploy: Triggers a new build from the connected repository
These are available from the Stores page menu and the Admin → Settings → Source Code page.
SSL / HTTPS
All domains served through Entaprenua use HTTPS by default. Custom domains should be configured behind a reverse proxy (nginx, Caddy) that provides SSL certificates (via Let's Encrypt or your own certificate).