ssdug / cvpz Goto Github PK

Currently AppVeyor does not support linux containers in docker. Travis does, so set one up.

The build should do the following things:

• Build the solution with the docker project enabled.
• Allow us to stand up the application in docker.
• Run tests against the standing instance of the application.
• Add build status badge to readme.md.
• Send build notifications to slack.

Use https://github.com/IdentityServer

Here are some extracted from the readme...

As consultants we are constantly needing to keep up our resumes updated with every engagement and the details of accomplishments. This isn't a terrible task as many of us have a git repository that holds and versions our resume well. Working in many contracts with local government poses a number of different time consuming tasks manually querying resume information to fill out matrix and other forms. The thought came to build a simple tool that can host this information in a format that allows us to automate this. Another benefit to this could be for consulting companies. For the small consulting shop it could be used to rapidly search consultants skills even availability for up coming contracts.

Note that I expect some of the things below to be thrown out as "don't care", but they're there just because.

Top-level requirements

• I need a way to add projects.
• Share my "resume" with other local consultants / consultant companies
• I would like to be able to query my resume by keyword, technology
• I would like to be able to export "reports"
• I would like to be able to import data from LinkedIn

On each project I would like to be able to...

• Add a job title
• Add a company/agency name
• Add a physical location
• Add a description
• Add a timeline
• Add a list of technologies used
• Add a timeline for each technology used
• Add technology-specific details of how it was used
• Add an industry or industries (ex. health-care, transportation)
• Add an approximate budget
• Add a point of contact for the project, including name, job title, phone, and email

Sharing sub-requirements*

• I should be able to share/hide certain pieces of information
• I would like a way to indicate how I should be contacted and my current availability
• I would like to be able to optionally opt-in/opt-out of some sort of "network" sharing

*This feature can expand to be quite large depending on the level of access control desired

"Reporting" requirements**

• I would like to be able to export a "Skills matrix"
• I would like to be able to generate a classic Resume
• I would like to be able to customize the header/footer of generated documents. (Note that the header and footer may not be consistent across document types)

**TBD: Document format: Excel, Html, *.docx?

When pulling the CVPZ source code, source for the CVPZ.Core and CVPZ.Web submodules are not in the src directory. I am not sure if that is your intention, but I thought it looked cluttered with the way it currently exists.

https://github.com/dotnet/eShopOnContainers/tree/master/src/Services/Identity/Identity.API

Currently our AppVeyor build is setup through @McLeopold's account. We should remove @McLeopold's account from the build chain. To do this we need a service account for GitHub.

Here are the steps I think are needed:

• Create new email account for service account.
• Create GitHub account using service account email.
• Add GitHub account to SSD organization.
• Signing into AppVeyor using GitHub service account.
• Create new build using the service account.
• Update encrypted slack token in the appveyor.yml.
• Update readme.md badge to point to new build's master branch.

We are going to use mssql-server-linux for this persistence layer.

If we are going to separate the UI as @CarBar mentioned. We will want to create new repo to house those files. This task should be for creating the repo, and creating the skeleton of the project.

@McLeopold @bivvo @TumboTheGnome
Should we have one place to manage tasks for all repos as we have a few now and there is not a single place for milestones, issues, etc...?

Trello? Any other free and awesome things out there?

When running docker-compose up, I get the following error. This could also be causing the Release CI build to fail. It has been disabled until we get this resolved.

C:\src\github\CVPZ [master ≡]> docker-compose.exe up
Creating network "cvpz_default" with the default driver
Building projects.api
Step 1/6 : FROM microsoft/aspnetcore:1.1
1.1: Pulling from microsoft/aspnetcore
693502eb7dfb: Pull complete
8fabf291b644: Pull complete
18885b0cc90b: Pull complete
a5edcabf023f: Pull complete
b4300fcff52c: Pull complete
Digest: sha256:72d4dadc7ee45f3a794a15a0642cc014fd75ca27c2e502c2d59719adea8300fd
Status: Downloaded newer image for microsoft/aspnetcore:1.1
 ---> 323bfc630f6a
Step 2/6 : ARG source
 ---> Running in f2683c545584
 ---> a823935addf9
Removing intermediate container f2683c545584
Step 3/6 : WORKDIR /app
 ---> 54042dfd29df
Removing intermediate container d10b833258ba
Step 4/6 : EXPOSE 80
 ---> Running in cedeaaf93d4a
 ---> caed3d6ee477
Removing intermediate container cedeaaf93d4a
Step 5/6 : COPY ${source:-obj/Docker/publish} .
ERROR: Service 'projects.api' failed to build: lstat obj/Docker/publish: no such file or directory

We have decided to begin with a .Net Core and Mongo setup. So we need to create docker files and .yml files.

Should look at getting a CI server during our heavy development phase. @CarBar thoughts?

Currently if people want to get into the SSDUG slack, someone has to send them an invite. This makes it prohibitively difficult for new people to join what is effectively a open chat.

Shayne Boyer setup a site that automatically sends invites out for the .NET Core Slack. It appears to use this codebase.

Let's look into setting this up for SSDUG

It is nice to have a section of the readme that describes how to get up and running with the codebase. Seeing as this project uses submodules, it might be problematic for new contributors to figure out how to pull ALL the source.

I believe it would be more clear to rename CVPZ to CVPZ.Core as we now have CVPZ.WebUI. This name would be more clear. Suggesting DotNetCore, and the Core portion of the application. I am curious to the thoughts of others.

We need to identify the individuals responsible for architectural decisions around feature sets. @CarBar could be responsible for everything but I think it would be more sustainable if we subdivided this responsibility.