view 3rdpartylibs.sh @ 567:f3452ce5c056

Make table writable for data import Lookup tables will probably be filled with data during import and thus should reside in the waterway schema, which is accordingly authorised. Touch only the one table relevant for bottlenecks here, as other data might be handled differently. Lookup tables referenced in out-commented columns not touched, as it is not yet clarified whether these columns will be removed completely. countries not touched neither, because it will be filled from different source and demo-data should have everything necessary to start importing bottlenecks.
author Tom Gottfried <tom@intevation.de>
date Tue, 04 Sep 2018 21:41:45 +0200
parents 4a637b333417
children d856e458dd64
line wrap: on
line source

#!/bin/sh
go get -u -v github.com/jackc/pgx
go get -u -v github.com/etcd-io/bbolt/...
go get -u -v github.com/mitchellh/go-homedir
go get -u -v github.com/spf13/cobra
go get -u -v github.com/spf13/viper
go get -u -v github.com/gorilla/mux
go get -u -v gopkg.in/gomail.v2
go get -u -v github.com/rs/cors
go get -u -v golang.org/x/net/html/charset