Backups

[CosmoMyzrailGorynych]

In GitLab by @CoMiGo on Feb 24, 2019, 20:45

Though ct.js already auto-saves the project to a recovery file, it would be great to save previous versions in separate files (similar to what YoYo GameMaker does).

Some things to consider:

• it should be configurable, both in the number of backups and in the fact of creating them at all. One will not need backups if they use git or other svn (probably).
• ideally, it should version assets, too. Maybe pack the project to a dated zip file?

[CosmoMyzrailGorynych]

In GitLab by @CoMiGo on Feb 24, 2019, 21:11

changed the description

[yonderbread]

Honestly I don't think it's necessary to incorporate backups into Ct.js, this should be up to the user to set up with an external program. It's best if each program a user has does 1 task instead of many, at least according to the Unix philosophy.

[CosmoMyzrailGorynych]

Ct.js is anything but Unix philosophy. And when you do lose a project, you will need this feature, because you won't have a thought about backing up these important files. Shortly, real-life and real deeds against logic.

The backup function surely needs a toggle, because it will conflict with the stuff you may use when you do set up external backups. (E.g. git, dropbox.)

[yonderbread]

Maybe integrating a simple git repo management interface/panel would be beneficial. A lot of users coming to Ct.js are new to programming and it would be awesome if it could introduce them to the world of version control systems.

[stale[bot]]

Hey there 👋 I marked this issue as stale as it hadn't brought much attention for quite a while. I do understand that stale issues are still issues, yet here stale issues receive the least attention from maintainers so they can focus on more relevant tasks. You can help with this issue by checking whether it affects latest versions of ct.js and writing about it if it does, providing an example project and steps to reproduce. Or maybe you can close it with a PR! Note that some platform-dependent issues can't be resolved by developers due to the absense of such devices :c We will need help from you for such tasks. If this issue won't get attention in three months, it will be closed.

[markmehere]

Not stale. I thought this too. Always disappointing to lose some code while transferring stuff.

[stale[bot]]

Hey there 👋 I marked this issue as stale as it hadn't brought much attention for quite a while. I do understand that stale issues are still issues, yet here stale issues receive the least attention from maintainers so they can focus on more relevant tasks. You can help with this issue by checking whether it affects latest versions of ct.js and writing about it if it does, providing an example project and steps to reproduce. Or maybe you can close it with a PR! Note that some platform-dependent issues can't be resolved by developers due to the absense of such devices :c We will need help from you for such tasks. If this issue won't get attention in three months, it will be closed.

[stale[bot]]

This issue is now closed! Please create a new one with a proper template if this issue still affects ct.js.