Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Using SQLite as default database engine
See original GitHub issueA modest suggestion. By default Admin uses SqlServer which has to be separately installed for anyone who doesn’t use Visual Studio daily.
Required changes would be pretty small:
UseSqlServer -> UseSqlite in StartupHelpers.cs and adding SQLite provider package for EntityFramework.Core.
I myself use PostgreSQL (works great), but for demonstration purposes I think SQLite would the best choice. This would also make checking out the Admin so much easier for Linux/MacOS folks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think that you could have it added to your migration documentation (where to change provider and what packages to add). Info on how you can use different providers (sqlserver, postgresql, sqlite) with default sqlite provider.
No, I’m using VS. But I’ve used VS Code for other .net core projects before and I could test if that works.