You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, we talked about needing to deploy JSON files for our ECE docs. Based on some prehistoric testing around 2017, we don't deploy JSON files, though Asciidoc has no problem referencing them. 🦖 🦖 🦖 From memory, the JSON files essentially get ignored.
As a workaround, we've been manually putting these files on S3 for the past few years, but it's an additional step release managers have to remember to do. It would be much easier if we could deploy whatever gets referenced in our docs source as part of the docs deployment to our servers.
I don't have any way to check the deployment code to see if we look just for specific file types like .html and .png to deploy only those, so the next step would likely be to do some more testing.
Recently, we talked about needing to deploy JSON files for our ECE docs. Based on some prehistoric testing around 2017, we don't deploy JSON files, though Asciidoc has no problem referencing them. 🦖 🦖 🦖 From memory, the JSON files essentially get ignored.
As a workaround, we've been manually putting these files on S3 for the past few years, but it's an additional step release managers have to remember to do. It would be much easier if we could deploy whatever gets referenced in our docs source as part of the docs deployment to our servers.
I don't have any way to check the deployment code to see if we look just for specific file types like .html and .png to deploy only those, so the next step would likely be to do some more testing.
@gtback ❤️
The text was updated successfully, but these errors were encountered: