A sample boilerplate of the .Net Core + React/Redux template for exclusively *nix machines with minimal prerequisites.
- Clone this repo
- Execute this command:
echo 'APP_DB_CONNECTION_STRING=Data Source=aspnet_core_react_redux-db,1433;Initial Catalog=AppDB;User ID=app_service;Password=app(!)STRONG_password;' >> .env - Execute
gem install docker-syncorsudo gem install docker-sync - Execute
docker-sync-daemon start && docker-compose up -d - In a separate terminal, execute
docker-compose logs -fand wait for .Net Core to come up, could take a minute or two at first run. - Execute
./docker/initdb - Browse to
http://localhost:5000 - Locally, open this repo in VS Code and start developing
docker-compose down && docker-sync-daemon stop
docker-compose logs && docker-sync-daemon logs
I've seen docker-sync get 😎 out of sync at times. This is generally solved by restarting Docker altogether and following the instructions from Step 4 above in Scaffolding/Development
- Any changes made to the project's directories will reflect automatically in the container
- This container runs
dotnet watch runwhich will keep track of both the SPA (underClientAppand .Net Code)- I'd recommend executing a
docker-compose logs -fto keep an eye on both the .Net and SQL Server container
- I'd recommend executing a
- You can open a bash into the .Net container by executing
./docker/dotnet/bash. From there, execute anydotnet add packagecommands you need- Your container should automatically restart/rebuild
- On your host machine, VS Code may ask to Restore Dependencies when you add/remove dependencies. Feel free to have VS Code update the dependencies on your host machine as well
- There is a convenience script:
./docker/dotnet/migrate. To use, simply execute./docker/dotnet/migrate MyMigrationName.- This will execute
dotnet ef migrations add MyMigrationNameanddotnet ef database updatein your .Net container
- This will execute
- As specified in the .env file you created when scaffolding, the Connection String is
APP_DB_CONNECTION_STRING=Data Source=aspnet_core_react_redux-db,1433;Initial Catalog=AppDB;User ID=app_service;Password=app(!)STRONG_password;
Being an ex-SQL Server guy, I know how good SSMS is -- I always argue it's one of the best database GUI's I've ever seen. However, in *nix world, we don't have the option of SSMS for convenience. What to do?
It turns out, jetBrains, the makers of the hugely popular ReSharper, WebStorm, and IntelliJ products have created a database GUI on top of IntelliJ called DataGrip. Coming from an ex-SSMS addict, I can safely say this is at parity with SSMS, and is in some cases superior to it!
This boilerplate uses Docker (specifically docker-compose) to install all infrastructure and prereqs that otherwise would take quite a bit of time to setup locally.
If you peek at the docker-compose.yml file, you'll see that we have Dockerfiles for .Net Core and SQL Server sitting in the /docker folder.
This custom Dockerfile for .Net Core brings in the latest LTS Node.js as of this writing (10.14.1) on top of the standard .Net Docker image.
This is important, as React needs Node.js installed to work properly.
This custom Dockerfile helps scaffold SQL Server with defaults to get going. You'll notice the username and password from the connection string we echo'd into the .env file on the root. Feel free to change the values to whatever you feel like.
This is simply an executable that launches a corresponding initdb under the sql-server folder. This creates the app DB, login, and user + dbo privileges via the sqlcmd utility. It will also execute an EF database update for the EF models.
You'll notice the gem install docker-sync as part of the initialization. In case you're curious, docker-sync is a utility that allows your host's filesystem (i.e. your dev machine) perform at native speed in a Docker container.
Without this utility, dotnet watch would execute file polling for changes, and would consume all of your container's resources. You may have seen this problem if you've tried Docker development using webpack-dev-server.