How to export a workspace from the free plan to import in a self-hosted version?
I just installed a version on my server and I would like to know if I can import a workspace that I had in the free version of Windmill there?
If there is any documentation on exporting and importing, as well as how to synchronize the entire workspace with GitHub, I would be grateful if you could point me in the right direction.
11 Replies
yes, it's in the docs, look for CLI and deploy from github
Version control from GitHub / GitLab | Windmill
At https://github.com/windmill-labs/windmill-sync-example you'll find an example repo that demonstrate how to use a github repo as source of truth for part or all of your Windmill workspace.
From what I understand, it is necessary for the repository to be public in order to have access to the "environments" menu. Is that correct?
Unfortunately, making the repository public to use "environment" could pose a risk by exposing the variables WMILL_URL and WMILL_WORKSPACE in yaml.
It may attract the attention of curious individuals who might attempt to exploit this endpoint on my server.
And, with the free GitHub account, it seems that configuring "environment" is not possible.
(https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment)
You absolutely don't need a public repo to use ENV variables. See https://docs.github.com/en/actions/learn-github-actions/variables
GitHub Docs
Variables - GitHub Docs
In the windmill tutorial has this image
"Add an environment "windmill" to the repository via the settings."
It seems not the same ENV variables.
or is it the same thing but in different ways?
I don't even have this Environments in a private GH repo I own. But I can set up secrets and variables in this tab.
Right. I set in this way now.
But I am experiencing a permission error when running the actions. I have been wondering if it has to do with the expected and configured Windmill environment in the workflow.
I found a way. I set the Workflow permissions (Settings -> Actions -> General) to
Reand and write permissions, instead of the default Read repository contents and packages permissions.
Maybe this could be added as a note in the documentation? If it's really correct. Here it ran like this.