You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be great if we would use a deployment method for the LGM website.
There are deployment services that can sync with a Github repository, so when we would push an update to the website source code, it would get pushed via FTP to the server.
One of those services – https://www.deployhq.com/ – is offering free accounts for open source projects. I guess that LGM could apply for that.
The benefits:
Makes collaboration easier.
Changes on the website can be tracked and reversed easily.
Not necessary to share FTP credentials with all site contributors.
The text was updated successfully, but these errors were encountered:
last weekend i've spent three hours working on that and came up with a simple self-hosted solution which achieves the same result, but the other way round:
I think it would be great if we would use a deployment method for the LGM website.
There are deployment services that can sync with a Github repository, so when we would push an update to the website source code, it would get pushed via FTP to the server.
One of those services – https://www.deployhq.com/ – is offering free accounts for open source projects. I guess that LGM could apply for that.
The benefits:
The text was updated successfully, but these errors were encountered: