Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #5399

Draft
wants to merge 2 commits into
base: production
Choose a base branch
from
Draft

Update README.md #5399

wants to merge 2 commits into from

Conversation

grantfitzsimmons
Copy link
Member

Fixes #5398

Copy link
Member

@maxpatiiuk maxpatiiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know that the non-docter installation instructions were likely out of date, but it was the only way for non-members to setup specify (since docker compositions are reserved for members). I understand that we can't prioritize non-members, but perhaps we can move the non-docker instructions into a separate .md file and add a disclaimer?

@PhatWheZ
Copy link
Collaborator

If you guys need assistance in refining and contributing to the docker-compositions keep me posted

@grantfitzsimmons
Copy link
Member Author

I know that the non-docter installation instructions were likely out of date, but it was the only way for non-members to setup specify (since docker compositions are reserved for members). I understand that we can't prioritize non-members, but perhaps we can move the non-docker instructions into a separate .md file and add a disclaimer?

We discussed this and can assist non-members with local installations of Specify as needed. We need to better track who is interested in our services and encourage them to use our recommended method: Docker. Local installations can be troublesome and involve many variables, making them difficult to manage and support if they become members. I want our software to be free to use and deploy, although access to the docker-compositions repository is a significant benefit of membership. We want to engage with anyone interested in using the software and can provide access based on specific needs.

@grantfitzsimmons
Copy link
Member Author

@PhatWheZ You are always welcome to suggest changes to that repository, especially if you have ideas for improvement! I am happy to review them and provide feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋Back Log
Development

Successfully merging this pull request may close these issues.

Improve README
3 participants