Amar Takhar commented: https://gitlab.rtems.org/groups/administration/-/epics/1#note_118949 I'm not so sure anymore, it may stay as docs.rtems.org for now once I get to that point and see what makes the most sense I will decide then. Basically, with GitLab CI we'll build the docs and create an artifact. That artifact gets 'deployed'. The cycle will be something like: * Receive MR. * Build docs and deploy to \`https://rtems.rtems.io/rtos/docs/rtems-docs/xxx * Once approved deploy file is deployed to either docs.rtems.org or docs.rtems.io The big sticking point is how docs are served from GitLab pages I'm not sure it's going to be a good idea to serve the docs from there or if it will be possible due to how we have our docs archives so it may just have to stick where it is now I can add a forward for docs.rtems.io to the page and we just keep `*.io` for pages deployments which is how gitlab.com works. -- View it on GitLab: https://gitlab.rtems.org/groups/administration/-/epics/1#note_118949 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
