The automatic workspaces based on files attached to articles.
-
I don't see a delete option for my work-spaces that were automatically created based on my article files. I press the cog (settings) and look around, but no delete. I'd like to just import from GitHub and start fresh, and then sync from Github periodically to keep the code up to date. Is that possible, or correct use of workspaces? Thanks in advance. PS: My theory is there is a coupling between the workspace and the article (downloads) that is inhibiting me from deleting the work-space and starting over. I am also having trouble deleting and adding new downloads to my article. Folks started complaining the zip files we're corrupted and so I wanted to fix them, but had a real hard time deleting the old files (they won't go away).
-
I don't see a delete option for my work-spaces that were automatically created based on my article files. I press the cog (settings) and look around, but no delete. I'd like to just import from GitHub and start fresh, and then sync from Github periodically to keep the code up to date. Is that possible, or correct use of workspaces? Thanks in advance. PS: My theory is there is a coupling between the workspace and the article (downloads) that is inhibiting me from deleting the work-space and starting over. I am also having trouble deleting and adding new downloads to my article. Folks started complaining the zip files we're corrupted and so I wanted to fix them, but had a real hard time deleting the old files (they won't go away).
Indeed, currently there is no delete option for workspaces attached to articles. They are quite locked. In future, however, that will change, we have plan to allow more flexible management for workspace-article connection. As for zips, Chris would need to speak about it, but as far as I know they expect you to keep the top-level folders (zips are created from them) untouched, if you have modified the folder structure on the top level article code might have problems figuring out how the zips should be created. When you have initialized git repo and you want to start over with different content, it is technically possible (as git is quite flexible here), though not really recommended, as it would require so-called history rewrite. I.e. people who already fetched out your git repo into their machines will have problems when you erase the history from server and replace it with different commits. Unfortunately thats the only help I can provide you at this moment. If you have some specifics, though, we'll try to push it forward. Like, which repo/zip is causing the trouble? What would you like to have instead?