I started my first project over at [prj:mqttchat]. I documented my steps in the hopes it will help others publish their first project, and to be used as a basis for improving the forge platform to make these steps even easier.
</project></forge></username>
- ... but it's empty
- in the code section of your forge project it has some suggested steps... but they are not customized to the cforge workflow. You've already checked out with cforge though.. so in windows explorer, navigate to C:\User\<username>\<forge neighborhood="" name="">,<project name="">,
</project></forge></username>
- make three new empty directories: trunk branches tags
- select the three of them, right click > TortoiseSVN... > add
- right click the C:\Users\<username>\<forge neighborhood="" name="">,<project name="">,
folder > cforge > commit.
</project></forge></username>
- Give it a commit message like "Just adding the default SVN folders"
- pop your .project (or .libs or whatever) in /trunk
- select all your files, right click > TortoiseSVN... > add
- right click the C:\Users\<username>\<forge neighborhood="" name="">,<project name="">,
folder > cforge > commit.
</project></forge></username>
- Give it a commit message like "First publicly available code, it currently does what it says on the tin most of the time"
- back in forge.codesys.com/<your project="">, go to Code and find the file you want people to download. right click and copy url</your>
- Edit your homepage for your project, describing how to use it, and include a [-download url=<copied_link> label=<the label,="" eg.="" project="">: missing =-]</the></copied_link>
- when you have the permission to, give it a license of UNLICENSE
- let people know about it on social media or forge.codesys.com/forge/talk
TODO: Investigate the forge .package mechanism described at https://forge.codesys.com/forge/wiki/Migrating%20Projects/