fossapps/starter.net

Starter kit for .NET

starter.net's Issues

user service

    public interface IUserService
    {
        Task<(SignInResult signInResult, User user)> AuthenticateByUsername(string username, string password);
        Task<(SignInResult signInResult, User user)> AuthenticateByEmail(string email, string password);
        Task<(SignInResult signInResult, User user)> Authenticate(string login, string password);
    }

Overwrite anything in appConfig using env variables

And a docs page where we'll define what each of them do and which env var can overwrite it.

use dll produced in produce_dll phase

user availability by endpoints

see if a user is available (for sign up), and if it's available for email as well.

build using latest dotnet core preview

make sure circle ci still passes

research email sending easily

we want a interface which should be implemented

docker-compose

add ILogger

need a decent logger, but don't want to get stuck to their ecosystem, https://dotnetthoughts.net/how-to-use-log4net-with-aspnetcore-for-logging/ for reference, simply create a class, which will initialize log4net, then we can add providers on top of log4net (a simple logger, accepting log4net instance seems better, because log4net would be configured easily instead of doing a new inside

setup linting

looks like there are many linting, have to decide which one should I choose

add skip-docker build msg

to avoid building too many images

Recaptcha Middleware

document circleci pipeline

with the docker tags

forgot password endpoint

when user requests a forgot password, send a token configured with jwt

move IdentityOptions configuration to config

use config file for this

multiple database support

There'll probably be a situation where we'll want to separate our read queries and write queries.

We need to have multiple database context, idea is to have 1 master db which only takes in writes, and N slave dbs which will be weighted and will be able to use weighted round robin for this.

Also add in a way so it's possible to do this, but if people don't want, should be easy to switch to simple 1 db as well.

update .NET version

there is new release of .NET now, so we need to update this project

rabbit mq client

use short commit sha

now it uses full commit hash, let's use short syntax so it's easy for people to pull

uuid provider (mw)

db config

move hard coded values to config

• should work normally when db is being queried (running docker-compose down && docker-compose up then starting project, should create a user in database, check it in adminer localhost:8081)
• should work when using migration from cli (dotnet ef database update --project ./Src/Starter.Net.Api/Starter.Net.Api.csproj --startup-project ./Src/Starter.Net.Api/Starter.Net.Api.csproj or dotnet ef database update should be able to apply migrations)

login endpoint

endpoint to login, it'll only log user in if user has verified email

Add Database

postgres for now

implement email client

implement interface which was done in #50 but make sure you register, add two implementations, one for mandrill's HTTP API (since it's an interface, we can implement later), and another for normal smtp configured with mailtrap.io

data structure for email

MailMessage should be used as content, include a builder for MailMessage with fluent API, and also include interface for email client.

Docker building

sign up

user should be able to sign up, but it should be locked by default

json everything

make sure all response is json, some of controllers are responding with string.

login endpoint is wrong

login endpoint is accepting data in body of post request, where it's supposed to use basic authentication

async everything

right now it's using everything as async, there are a lot of void types, we need to return whatever database returns and make sure we have async all the time.

user repository

add a user repository so we can query for users

only build docker image on PRs if a label is present

If we build all PRs and each push, we'll end up with too many docker images and tags.

Tags and master should be built always, but each PR doesn't need to.

If it's needed, contributor can add a specific label which build will check and tag if present.

In case build finishes before addition of this tag, contributor adds label, then restarts circleci's final build step in the pipeline and it should tag it.

documentation

setup CI

list sessions

startup base's constructor isn't same as startup in Api project

auth

• login
• log out
• signup
• forgot password

publish built tag to docker hub

We need to login and publish to registry.
In future we can trigger postman tests which tests this current image with our tests, but for now only commenting with a predefined template will be good.

add location service

Add Location with lat long on our table, create a new domain called Location, everything will go inside this, make sure database is partial so we can add our db set from this domain.

IRolesRepository

    public interface IRolesRepository
    {
        IdentityUserRole<string>[] GetRolesByUserId(string userId);
    }

app-metrics

setup app metrics with basic stuff

delete sessions

comment PR (if available) with published tag

while making a comment don't create a new comment, always use same comment, first time we can add a new comment, and after that we can edit same comment to add new info.

To store metadata we can use comments like probot-metadata

config to create new users

instead of creating hardcoded admin user, use a config for that

reset password with valid token

user should be able to set a new password if the token is valid and is for the user.