Comments

• 

  9 days ago by mgrifalconi | Reply

  Invested quite some time trying to have a hosted tool that: - takes url, adds them to database, hosts the sqlite view tool But found the following issues: - gets complicated fast, putting stuff into container, needing to work on CI to keep things up to date, etc. - a single instance does not work for multiple users, one might want only some information in the database so it should have some sort of user authentication and keep different databases for each user.

  I think, given the current niche use case of the tool, KISS principle should be the priority and I will not use the various complex adaptation that I tried during these days. I will just add the sql lite viewer as part of the project, so users do not need to use an external service (even though runs locally on browser anyway).

×
Edit Comment 12162
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Invested quite some time trying to have a hosted tool that: - takes url, adds them to database, hosts the sqlite view tool But found the following issues: - gets complicated fast, putting stuff into container, needing to work on CI to keep things up to date, etc. - a single instance does not work for multiple users, one might want only some information in the database so it should have some sort of user authentication and keep different databases for each user. I think, given the current niche use case of the tool, KISS principle should be the priority and I will not use the various complex adaptation that I tried during these days. I will just add the sql lite viewer as part of the project, so users do not need to use an external service (even though runs locally on browser anyway).
 
×
Reply to mgrifalconi
Invested quite some time trying to have a hosted tool that: - takes url, adds them to database, hosts the sqlite view tool But found the following issues: - gets complicated fast, putting stuff into container, needing to work on CI to keep things up to date, etc. - a single instance does not work for multiple users, one might want only some information in the database so it should have some sort of user authentication and keep different databases for each user.
I think, given the current niche use case of the tool, KISS principle should be the priority and I will not use the various complex adaptation that I tried during these days. I will just add the sql lite viewer as part of the project, so users do not need to use an external service (even though runs locally on browser anyway).
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview