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

Cleanup repo for local dev #69

Open
TimothyStiles opened this issue Apr 4, 2023 · 3 comments · May be fixed by #81
Open

Cleanup repo for local dev #69

TimothyStiles opened this issue Apr 4, 2023 · 3 comments · May be fixed by #81
Assignees

Comments

@TimothyStiles
Copy link
Contributor

TimothyStiles commented Apr 4, 2023

The current repo is kind of a prototyping mess. I'd like to see it trimmed down and refactored such that a dev can get a basic setup running on their computer with a one line install like they would experience with Gitea (a well loved self-hostable git server with simple one line install).

@TimothyStiles
Copy link
Contributor Author

config for pre-filter of choice organisms. <-

@isaacguerreir isaacguerreir linked a pull request Apr 5, 2023 that will close this issue
@isaacguerreir isaacguerreir linked a pull request Apr 5, 2023 that will close this issue
@TimothyStiles TimothyStiles moved this to In Progress in Ark roadmap Apr 5, 2023
@isaacguerreir
Copy link
Collaborator

isaacguerreir commented Apr 5, 2023

Now my definition of basic setup will be:

  1. Installing ark
  2. Running ark command
  3. A check will be executed to search for a config file
  4. If not found ark will run an interactive config setup
  5. Finally it will run the database setup based on config

Tasks:

  • Check if a config file is present
  • If not found go to interactive config setup
  • Run the database setup based on config

Open to discussing if someone thinks another way.

@TimothyStiles
Copy link
Contributor Author

Now my definition of basic setup will be:

1. Installing ark

2. Running `ark` command

3. A check will be executed to search for a config file

4. If not found `ark` will run an interactive config setup

5. Finally it will run the database setup based on config

Tasks:

* [ ]  Check if a config file is present

* [ ]  If not found go to interactive config setup

* [ ]  Run the database setup based on config

Open to discussing if someone thinks another way.

Seems good to me @isaacguerreir!

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 a pull request may close this issue.

2 participants