I just finished import ability. I tested it locally and it works fine. However some other tests should be great.

Also I am not sure if I explained well how to import in readme. Can you anyone check it out?

This issue is related with #124

Is your feature request related to a problem? Please describe. Now we have multi user system. However we don't have any activation process for users.

Describe the solution you'd like When users signup, system should send activation email to user. And when user click on activation link, system should activate user.

Describe the bug Hi,

I got an issue while starting Passwall server. I have actual docker-compose file, I added two service in it for Passwall Server and Postgres. Postgres is working healty but Passwall Server is looping on restarting.

You can find the error logs from the container:

standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error

Docker-Compose File

  passwall-db:
    container_name: passwall-db
    image: postgres:alpine
    hostname: passwall-db
    networks:
      saasnet:
        aliases:
        - passwall-db
    restart: on-failure
    env_file:
    - passwall.env
    volumes:
    - /root/docker/passwall-db:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 5s
      timeout: 5s
      retries: 5
      start_period: 5s
  passwall-server:
    container_name: passwall-server
    image: passwall/passwall-server:latest
    hostname: passwall-server
    networks:
      saasnet:
        aliases:
        - passwall-server
    restart: always
    env_file:
    - passwall.env
    build:
      context: .
    depends_on:
      passwall-db:
        condition: service_healthy
    volumes:
    - /root/docker/passwall-server:/app/config

OS Verison

root@xxx:~/docker# uname -a
Linux xxx 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
root@xxx:~/docker# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:        20.04
Codename:       focal
root@xxx:~/docker# 

Docker Verison

root@xxx:~/docker# docker version
Client: Docker Engine - Community
 Version:           20.10.9
 API version:       1.41
 Go version:        go1.16.8
 Git commit:        c2ea9bc
 Built:             Mon Oct  4 16:08:29 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.9
  API version:      1.41 (minimum version 1.12)
   o version:       go1.16.8
  Git commit:       79ea9d3
  Built:            Mon Oct  4 16:06:37 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.11
  GitCommit:        5b46e404f6b9f661a205e28d59c982d3634148f8
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
   ersion:          0.19.0
  GitCommit:        de40ad0

root@xxx:~/docker# docker compose -verison
docker-compose version 1.29.2, build 5becea4c

If you need any further logs please don't hesitate to contact me.

Thanks.Regards

Is your feature request related to a problem? Please describe.

It is NOT a feature but could be nice to do, first of all, I am not very deep into project, which means that if I am suggesting something which is not valid or wrong, please let me know and forgive me. I have following concerns on overall repo, it may valid or not valid. (depends person to person) However, just wanted to share.

Concerns;

• is not it a little bit odd that main.go is under cmd/pass-wall folder ? is there any intention or plan to write down CLI as well ?

• I have noticed that all go files ends with _api.go suffix here. Is it really necessary ? Since it is under api dir, no need to add suffix. (according to best practices )

• I think, there is an overdue or invalid todo for instance here, it is deprecated, can be read from here

Describe the solution you'd like

• Move main.go to root directory. (or prepare a CLI for the repo)
• Remove suffixes from files under api dir
• Handle given todo regarding to Public-Key-Pins in different way.

Is your feature request related to a problem? Please describe. We don't know if the server is running. We need a public (excluded from auth) endpoint to check server status. Then we can use uptimerobot and check the server status regularly.

Describe the solution you'd like

We need an endpoint which only returns 200 with a GET method. It should be /ping, /health or /health-check. We can search for best practice about it.

For a better health check, this endpoint can check if postgres or mysql is running and db connection is fine.

Additional context Does anyone want to work on this?

API needs a backup plan. Any ideas? For SQL lite file, it can be stored (icloud, google folder etc.) anywhere but what about Postgres and MySQL databases? I think there can be a cron job which gets the backup of dataabse table.

Hi, i created an account on gpass.io to see how is made. i think has some very nice features:

###Types you can create types with predefined fields. This allows for multiple type of credentials.

###Folders you can group credentials into folders.

###Tags very useful

###Adding new fields for same entry on every credentials you can have new fields, dynamically added.

if you consider adding this support, it should be structured at the begging.

login.Password is a string in the struct, butencrypt func generating the binary data for store in the login.Password, if you use postgresql (maybe mysql too) it throwing the invalid byte sequence error (here)

I think login model needs to gorm column type tags, postgresql uses bytea type for that.

User should export all logins as csv file.

Endpoint: /logins/export Method: POST

Example csv file:

URL,Username,Password
http://dummy.com,dummyuser,dummypassword
http://dummyweb.com,dummyuser2,dummypassword2

Is your feature request related to a problem? Please describe.

Update git remote address and update broken link.

Describe the solution you'd like

Change upstream git remote address in CONTRIBUTING-TR.md hoodiehq -> passwall as done in CONTRIBUTING.md

Change "şuradan" link of "Açık kaynak projeye nasıl katkıda bulunulabileceğini anlatan daha detaylı bir dokümana şuradan ulaşabilirsiniz."

https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github -> https://app.egghead.io/playlists/how-to-contribute-to-an-open-source-project-on-github

Passwall Server has support for on-premise installation with Docker. To do this we have a docker-compose.yml file which has 2 services: passwall-server and postgres. However we need to add Nginx for reverse proxy. Also We need to easly generate SSL certificate with Let's Encrypt or user can add his/her own certificate via volumes.

I found this article which can give some ideas about the issue: https://www.digitalocean.com/community/tutorials/how-to-deploy-a-go-web-application-with-docker-and-nginx-on-ubuntu-18-04

Anyone wants to work on this?

The ubuntu-18.04 environment is deprecated, consider switching to ubuntu-20.04(ubuntu-latest), or ubuntu-22.04 instead.

For more details see https://github.com/actions/virtual-environments/issues/6002

Is your feature request related to a problem? Please describe. No

Describe the solution you'd like A random password generator like https://www.lastpass.com/password-generator

Describe alternatives you've considered https://www.lastpass.com/password-generator

Additional context It can be find on here https://www.lastpass.com/password-generator

Is your feature request related to a problem? Please describe. I'm bored to share my password to all people that need it. If I've a password to connect to a shared server account for company, It need to be accessed to the same password entry by multiple user.

Describe the solution you'd like I want to share a password with a group of people, registred on the same instance, and updated to all account if I change it.

That allow Organisation account, like LastPass allow it (for organisation account).

Is your feature request related to a problem? Please describe.

Not feature but requirement, it is clear that coverage level of the repo could be improved by increasing number of unit tests. It can provide more flexibility and easy debugging from code base without requirement of running server from scratch.

Describe the solution you'd like

• Add more tests where possible

Describe alternatives you've considered

• No alternative solution at the moment.

It would be nice to integrate Goreleaser process into CI/CD step to have automated release action with tagged commit.

Proposal

• With integration of (Github actions) (could be ? or Travis CI does not matter very much ) + Goreleaser, the process of releasing new version would be much convenient.

• Having Goreleaser in pocket means that uploading necessary binary to homebrew (or another package manager ) will be much easy than anticipated. Seems, homebrew issue #30 has been assigned to @patyogesh however with this approach, it is possible to shot two birds (-tasks-) with one stone :)

@patyogesh, would like to have comment on it ? I have no glue about the process of your development at the moment however if you think or might think in same way , we can figure out something in common. Otherwise, this issue can also close #30.

Any suggestion, comment, or improvement related to this issue is very welcome !