The only required piece to be regularly upgraded is our CLI.
If you created an instance before March 15, please note the dates below.
On March 31, and April 10, respectively, subdomains URLs <subdomain>.us.openode.io and <subdomain>.fr.openode.io will be deprecated in favor of <subdomain>.openode.io.
When you use the new system, the nameservers ns1/2.vultr.com are no more updated.
You have to use the DNS settings provided at the end of the deployment or in the administration > Instances > Settings > DNS and Aliases.
The CLI, which is a regular NPM package, can be upgraded with:
npm i -g openode
Note that you can skip the following steps if you just destroy your instance, remove Dockerfile, and recreate a new one.
The following steps should be done:
openode del-location <current location>
If you don't know the location you can use:
openode add-location usa
On March 2020 we made a new major version of our deployment system. Therefore, if you had instances before March 2020, you have to upgrade them as follows.
First you have to set the following configuration:
openode set-config TYPE kubernetes
Next, make sure to back up your Dockerfile:
mv Dockerfile Dockerfile.bak
Then apply the new template (this will generate a Dockerfile):
If you want to manually upgrade your Dockerfile, the only difference is that you need to copy the files in the images, and also packages can be installed directly. If we take the new Node.js template:
FROM node:12-alpine WORKDIR /opt/app # daemon for cron jobs RUN echo 'crond' > /boot.sh # RUN echo 'crontab .openode.cron' >> /boot.sh # Install app dependencies # A wildcard is used to ensure both package.json AND package-lock.json are copied # where available (npm@5+) COPY package*.json ./ # *** Copy the package.json in the image RUN npm install --production # *** Install packages in the image # Bundle app source COPY . . # *** Copy all files in the image EXPOSE 80 CMD sh /boot.sh && npm start