421a71e145
Our docker python-base image is a python3 image where python and python3 point to the same version of python which happens to be a 3.x depending on the specific base image. One of the things that came up at the PTG is that we'd like to start identifying where we use python2 in order to port to python3. That is made a bit more difficult when we use `python` assuming it is `python3` as we do in our docker images. Update the images to use `python3` to make this a lot more explicit and clear that we don't need to port these items. Change-Id: I54e8f128f0cb8fbbdf54e3748384470262bef3a9
37 lines
1.1 KiB
Bash
Executable File
37 lines
1.1 KiB
Bash
Executable File
#!/bin/sh
|
|
|
|
# Copyright 2018 Red Hat, Inc.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
|
|
# Create directories needed by gitea
|
|
mkdir -p /data/git
|
|
chown 1000:1000 /data/git
|
|
|
|
mkdir -p /data/gitea
|
|
chown 1000:1000 /data/gitea
|
|
|
|
mkdir -p /data/gitea/ssl
|
|
chown 1000:1000 /data/gitea/ssl
|
|
chmod 0500 /data/gitea/ssl
|
|
cp /secrets/gitea_tls_cert /data/gitea/ssl/cert.pem
|
|
cp /secrets/gitea_tls_key /data/gitea/ssl/key.pem
|
|
|
|
# This one is used by openssh and can remain root-owned
|
|
mkdir -p /data/ssh
|
|
|
|
# Template the config file (which can also be root-owned)
|
|
export JINJA_SRC_FILE=/config_src/app.ini.j2
|
|
export JINJA_DEST_FILE=/conf/app.ini
|
|
python3 /run.py
|