Skip to content

Commit 94136dc

Browse files
committed
add deployment steps and Contrib details
1 parent 1faa4a3 commit 94136dc

File tree

4 files changed

+156
-75
lines changed

4 files changed

+156
-75
lines changed

CONTRIBUTING.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
# Contributing
2+
3+
When contributing to this repository, please first discuss the change you wish to make via issue,
4+
email, or any other method with the owners of this repository before making a change.
5+
6+
Please note we have a code of conduct, please follow it in all your interactions with the project.
7+
8+
9+
## Code of Conduct
10+
11+
### Our Pledge
12+
13+
In the interest of fostering an open and welcoming environment, we as
14+
contributors and maintainers pledge to making participation in our project and
15+
our community a harassment-free experience for everyone, regardless of age, body
16+
size, disability, ethnicity, gender identity and expression, level of experience,
17+
nationality, personal appearance, race, religion, or sexual identity and
18+
orientation.
19+
20+
### Our Standards
21+
22+
Examples of behavior that contributes to creating a positive environment
23+
include:
24+
25+
* Using welcoming and inclusive language
26+
* Being respectful of differing viewpoints and experiences
27+
* Gracefully accepting constructive criticism
28+
* Focusing on what is best for the community
29+
* Showing empathy towards other community members
30+
31+
Examples of unacceptable behavior by participants include:
32+
33+
* The use of sexualized language or imagery and unwelcome sexual attention or
34+
advances
35+
* Trolling, insulting/derogatory comments, and personal or political attacks
36+
* Public or private harassment
37+
* Publishing others' private information, such as a physical or electronic
38+
address, without explicit permission
39+
* Other conduct which could reasonably be considered inappropriate in a
40+
professional setting
41+
42+
### Our Responsibilities
43+
44+
Project maintainers are responsible for clarifying the standards of acceptable
45+
behavior and are expected to take appropriate and fair corrective action in
46+
response to any instances of unacceptable behavior.
47+
48+
Project maintainers have the right and responsibility to remove, edit, or
49+
reject comments, commits, code, wiki edits, issues, and other contributions
50+
that are not aligned to this Code of Conduct, or to ban temporarily or
51+
permanently any contributor for other behaviors that they deem inappropriate,
52+
threatening, offensive, or harmful.
53+
54+
### Scope
55+
56+
This Code of Conduct applies both within project spaces and in public spaces
57+
when an individual is representing the project or its community. Examples of
58+
representing a project or community include using an official project e-mail
59+
address, posting via an official social media account, or acting as an appointed
60+
representative at an online or offline event. Representation of a project may be
61+
further defined and clarified by project maintainers.
62+
63+
### Enforcement
64+
65+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
66+
reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
67+
complaints will be reviewed and investigated and will result in a response that
68+
is deemed necessary and appropriate to the circumstances. The project team is
69+
obligated to maintain confidentiality with regard to the reporter of an incident.
70+
Further details of specific enforcement policies may be posted separately.
71+
72+
Project maintainers who do not follow or enforce the Code of Conduct in good
73+
faith may face temporary or permanent repercussions as determined by other
74+
members of the project's leadership.

README.md

Lines changed: 82 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,84 @@
1-
## Note Bookmark
1+
# Note Bookmark
22

33
[![.github/workflows/azure-dev.yml](https://github.com/FBoucher/NoteBookmark/actions/workflows/azure-dev.yml/badge.svg)](https://github.com/FBoucher/NoteBookmark/actions/workflows/azure-dev.yml)
4+
5+
I use this project mostly everyday. I build it to help me collecting my thoughts about articles, and blob posts I read during the week and then aggregate them in a #ReadingNotes blog post. You can find those post on my blog [here](https://frankysnotes.com).
6+
7+
NoteBookmark is composed of three main sections:
8+
9+
- **Post**: where you can manage a posts "to read", and add notes to them.
10+
- **Generate Summary**: where you can generate a summary of the posts you read.
11+
- **Summaries**: where you can see all the summaries you generated.
12+
13+
![Slide show of all NoteBookmark Screens](gh/images/NoteBookmark-Tour_hd.gif)
14+
15+
## How to deploy Your own NoteBookmark
16+
17+
### Get the code on your machine
18+
19+
- Fork this repository to your account.
20+
- Clone the repository to your local machine.
21+
22+
### Create the Azure Storage
23+
24+
Curretly the project assumed you already have an Azure Storage account, therefor its creation is exclude of the deployment. Let's create one now and retreive it's ConnectionString using a Azure CLI comnand (you can also use the Azure Portal is you prefer).
25+
26+
Here in Bash:
27+
28+
```bash
29+
resourceGroupName="notebookmark-dev"
30+
location="eastus"
31+
storageAccountName="notedata"
32+
33+
az group create --name $resourceGroupName --location $location
34+
35+
az storage account create --name $storageAccountName --resource-group $resourceGroupName --location $location --sku Standard_LRS
36+
37+
az storage account show-connection-string --name $storageAccountName --resource-group $resourceGroupName
38+
```
39+
40+
and PowerShell:
41+
42+
```powershell
43+
$resourceGroupName = "notebookmark-dev"
44+
$location = "eastus"
45+
$storageAccountName = "notedata"
46+
47+
az group create --name $resourceGroupName --location $location
48+
49+
az storage account create --name $storageAccountName --resource-group $resourceGroupName --location $location --sku Standard_LRS
50+
51+
az storage account show-connection-string --name $storageAccountName --resource-group $resourceGroupName
52+
```
53+
54+
Save this connection string, you will need it later.
55+
56+
### Deploy the soluiton
57+
58+
Using Azure Developer CLI let's initialize your environment. In a terminal, at the root of the project, run the following command. When ask give it a name (ex: NoteBookmark-dev).
59+
60+
```bash
61+
azd init
62+
```
63+
64+
Now let's deploy the solution. Run the following command in the terminal. You will have to select your Azure subscription where you want to deploy the solution, a location (use the same as for the storage creation earlier), and paste the connection string you saved earlier when asked for the 'data_storage_connstr'.
65+
66+
```bash
67+
azd up
68+
```
69+
70+
It should take around five minutes to deploy the solution. Once it's done, you will see the URL for **Deploying service blazor-app**.
71+
72+
### Secure the App
73+
74+
The app is now deployed, but it's not secure. Navigate to the Azure Portal, and find the Resource Group you just deployed (ex: rg-notebookmark-dev). In this resource group, open the Container App **Container App**. From the left menu, select **Authentication** and click the **Add identity provider**.
75+
76+
You can choose between multiple providers, I like to use Microsoft since it's deploy in Azure and I'm already logged in. If Microsoft is choose, select the recomended **Client secret expiration** (ex: 180 days). You can keep all the other default settings. Click **Add**.
77+
78+
Next time you will navigate to the app, you will be prompt a to login with your Microsoft account. The first time you will have a **Permissions requested** screen, click **Accept**.
79+
80+
Voila! Your app is now secure.
81+
82+
## Contributing
83+
84+
Your contributions are welcome! Take a look at [CONTRIBUTING](/CONTRIBUTING.md) for details.

gh/images/NoteBookmark-Tour_hd.gif

54.5 MB
Loading

next-steps.md

Lines changed: 0 additions & 74 deletions
This file was deleted.

0 commit comments

Comments
 (0)