Soā¦ one for the ācontentā folder and other for everything else. Simple.
Letās call them āmainā and ācontentā.
Since I wonāt be using Gitlab what is the best way I wonderā¦ because the folders below will be modified when new users are created by kirbyās user account system (the site will allow users to create accounts (without panel access):
assets/avatar
thumbs
sites/accounts
I was thinking about having the basic setup of localhost / dev subdomain (stage) / live (production) environments and now Iām worried about the repos getting conflicts after the site goes live.
Is it even recommended to keep the āmainā repo in sync between these environments (local/dev/live) by some pulling/pushing strategy?
I like the idea of the panel not being public accessible (live/production) but it would change the whole deploy strategyā¦ Iād prefer lesser complex solutions.
Alsoā¦ should the ācontentā repo be a submodule of the āmainā?
What about the ācontentā repoā¦ should it contains the folder ā/contentā itself or only its contents?
I have no objections for using deployment services like dploy.io (have used it before in non-kirby projects). But also have seen webhooks, node scripts and even rsync solutions here in the forumā¦
But in a later post they acknowledge that depending of the way youāre going to publish/deploy (ftp/sftp) the symlinks wonāt work due to protocol incompatibility.
In a previous blog post we showed how Kirby plugins can be managed as Git submodules. This practice could be followed here, too! But for simplicity weāll install the plugin the conventional way. Besides, we had to experience the unfortunate incompatibility of symlinks and FTP with some of our client projects, so, while offering less maintainability, the conventional way is more robust.
I read this post, itās great! It wood be good to hear about other opinions/methods so we can choose the most appropriate, or pick the parts that suit our projects best.
Files and folders can be a bit confusing in Kirby, especially compared to most CMSes where you have a clear place for themes (btw is there such thing as a pluggable theme in Kirby?) and libraries.
There are many ways to do it, and itās not always easy to choose the right one.
Iām working on my first Kirby powered site and was just thinking about the issue of deploying with git without overwriting content changes made by a user through the panel.
How do most people deal with this? For this particular project I really donāt want to use a cron triggered git commit because Iām not the main server admin and Iām worried about someone removing the cron job one day and content getting overwritten.
Interested in solutions as well!
Ideally with how to deal with an FTP-only access to the online version of the websiteā¦
Best practices anyone?
(Iāve spent the last 4 hours merging āby handā my local and online version and I donāt really want to do that again )
Take a look at https://github.com/git-ftp/git-ftp, I donāt have any experience with this tool myself but might be worth checking out. Donāt know if it supports submodules, though.
Also, as @Malvese mentioned, popular FTP clients usually come with sync features, if you are not on a Mac, have a look at the open source tool FileZilla or similar ā¦
.
)