https://github.com/healingdrawing/task-social-network
TypeScript front-end(Vue3 Composition API + pinia). Golang back-end. Social network. Profile, posts, chats, groups, admin panel. grit:lab Åland Islands 2023
https://github.com/healingdrawing/task-social-network
admin-panel authentication chat database-migrations golang groups pinia posts profile sqlite3 typescript vue3-composition-api vue3-typescript websocket
Last synced: about 1 year ago
JSON representation
TypeScript front-end(Vue3 Composition API + pinia). Golang back-end. Social network. Profile, posts, chats, groups, admin panel. grit:lab Åland Islands 2023
- Host: GitHub
- URL: https://github.com/healingdrawing/task-social-network
- Owner: healingdrawing
- License: mit
- Archived: true
- Created: 2023-06-08T15:58:10.000Z (about 3 years ago)
- Default Branch: zero
- Last Pushed: 2024-10-29T16:21:46.000Z (over 1 year ago)
- Last Synced: 2025-03-12T00:34:45.500Z (over 1 year ago)
- Topics: admin-panel, authentication, chat, database-migrations, golang, groups, pinia, posts, profile, sqlite3, typescript, vue3-composition-api, vue3-typescript, websocket
- Language: Go
- Homepage:
- Size: 2.51 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# task-social-network
After run project, open the browser on `http://localhost:3000/`
## audit run to show containers
To show two docker containers inside docker desktop or terminal, one for backend, and one for frontend (docker desktop must be started before), inside root folder of repository where `run.sh` placed, using terminal execute command:
- `./run.sh`
to show containers in terminal:
- `docker ps -a`
## dev run
### backend
- `cd backend`
- `go run .`
### frontend
- `cd frontend`
- `npm i`
- `npm run serve`
## At the moment the recomendations are:
- DO NOT USE `zero` branch, which is default, it can be used later as final destination
- use your own branches , and merge them into `dev` branch, using pull requests
- start branches from "wip/" prefix, f.e.: `wip/the-name-of-branch` or from the "futures/" prefix, f.e.: `futures/my-new-success`
- before start work session always refresh you local branch from remote, to not forget something or do not recreate the same twice
- after work session completed, even if the code not very polished, you should commit your changes into your branch to do not loose the local progress on the other computer(when you will open repo from other workplace), even if code is not very polished at the moment. It is your branch and you can use it as you want
## task description and audit questions, on github
https://github.com/01-edu/public/tree/master/subjects/social-network
# According to task requirements, at the moment, there is no any restrictions for connection type, and level of privacy of the project.