Painting on Glass
Painting on Glass is the second studio album by The 3rd and the Mortal.
Painting on Glass | ||||
---|---|---|---|---|
Studio album by | ||||
Released | January 19, 1996 | |||
Genre | Experimental music, doom metal | |||
Length | 64:02 | |||
Label | Voices of Wonder | |||
Producer | Lars Lien Tor Breivik The 3rd and the Mortal | |||
The 3rd and the Mortal chronology | ||||
|
Track listing
- "Magma" - 4:25
- "Commemoration" - 5:41
- "Crystal Orchids" - 2:59
- "Persistent and Fleeting" - 5:58
- "White Waters" - 2:50
- "Aurora Borealis" - 1:32
- "Dreamscapes" - 4:31
- "Aurora Australis" - 2:39
- "Azure" - 4:00
- "Veiled Exposure" - 5:22
- "Stairs" - 2:27
- "Eat the Distance" - 7:11
- "Vavonia, part II" - 7:23
- "Horizons" - 7:04
Credits
Band
- Rune Hoemsnes – Drums and percussion
- Bernt Rundberget – Bass-guitars
- Ann-Mari Edvardsen – Vocals, keyboards
- Trond Engum – Electric and acoustic guitars
- Geir Nilssen – Electric and acoustic guitars, keyboards
- Finn Olav Holthe – Guitar treatments, acoustic guitar, keyboards, tapes
Additional Musicians
- Ola Evensen – Trombone
- Lars Lien – Mellotron and ARP synth
- Oddrun Solberg – Church organ
- Aksel Hagen Tjora – Didjeridoo
- Sigurd Engum – Waterbucket
- Øyvind Klungseth Zalsen – Keyboards
- Monika Edvardsen – Additional vocals
gollark: They aren't that hard. You just use `server_name` in the `server` block.
gollark: Not specifically wordpress, no.
gollark: I would probably use nginx, because I'm used to it and it has nicer configuration:```nginxhttp { # whatever important configuration you have for all HTTP servers, `nginx.conf` probably ships with some # fallback in case someone visits with an unrecognized Host header server { listen 80 default_server; listen [::]:80 default_server; return 301 http://somedomain$request_uri; } server { listen 80; # you may (probably do) want HTTPS instead, in which case this bit is somewhat different - you need to deal with certs and stuff, and use port 443 - also you should probably add HTTP/2 listen [::]:80; # IPv6 server_name domain1.com; location / { proxy_pass http://backend1:8080/; } } server { listen 80; listen [::]:80; server_name domain2.com; location / { proxy_pass http://backend2:8080/; } }}```
gollark: The reverse-proxy solution is in my opinion the best one, although it would require some config.
gollark: I think LetsEncrypt may not be very happy with that, though.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.