Skip to content

Conversation

@ocdtrekkie
Copy link
Collaborator

I'm not including this in 1.2, but leaving this PR out there in part as a reminder to do it next release. There is no Sandstorm Development Group, Inc. so we should rename this. It shows up in the legacy Control Panel primarily.

@ocdtrekkie ocdtrekkie added this to the vagrant-spk 1.3 milestone Mar 16, 2024
@ocdtrekkie
Copy link
Collaborator Author

One thing that bugs me is the installer refers to an "app URL" for support and updates, and it points at docs.sandstorm.io. I want to change this, but the docs is probably the best place for support, and the GitHub would be the best place for updates, but I don't want to put a GitHub link there or have to add a separate URL to the config for this.

I am sort of wondering if we should have a "landing page" for some of our project tools on sandstorm.org with some of the basic information and links. Something like a sandstorm.org/vagrant-spk which links to the latest downloads, the right docs files, etc.

@neuroradiology
Copy link

Agree with this change in attribution of publication.

I love the idea of a landing page for sandstorm.org, which can point back to sandstorm.io resources that are still valid, but to the org domain where appropriate. A single canonical reference for the status of the project would be incredibly helpful, IMO, and the landing page could be it.

@ocdtrekkie
Copy link
Collaborator Author

I have a draft of the landing page here: https://vagrant-spk-landing.sandstorm-website-684.pages.dev/vagrant-spk (Apparently I started this a while ago and never finished it.) Up to "Step 1" is correct, the rest is just the normal Sandstorm install instructions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants