Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week
Source: dev.to
Separate content from config in Statamic
Before we continue with the deployment, we need to make some adjustments. As stated before, my goal is to separate content from config as much as possible.
My approach: User editable content (markdown files, media assets in content/) should only be stored on the production server, they shouldn't be tracked in the git repository. Only configuration files should be tracked and pushed via git, always from local to production in a one-way-street.
But how do we get the production content data to the local development environment to play and develop with it?
My approach: User editable content (markdown files, media assets in content/) should only be stored on the production server, they shouldn't be tracked in the git repository. Only configuration files should be tracked and pushed via git, always from local to production in a one-way-street.
But how do we get the production content data to the local development environment to play and develop with it?
Newsletter
ToastMail
Achieve superior email deliverability with ToastMail! Our AI-driven tool warms up inboxes, monitors reputation, and ensures emails reach their intended destination. Sign up today for a spam-free future.
Community Partners
Laravel/PHP Careers