gfwleak/stellar-stellar-dev-env
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

🎉 init(first commit):

Browse Source
This commit is contained in:
yangwei
2024-02-26 19:26:43 +08:00
parent d6cec34bb7
commit f467df42ec
6 changed files with 152 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
.gitlab-ci.yml Normal file
View File

@@ -0,0 +1,16 @@
image: docker:stable
variables:
IMAGE_TAG: $CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG
before_script:
- docker info
- docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
build:
stage: build
script:
- docker build -t $IMAGE_TAG .
- docker push $IMAGE_TAG
tags:
- share

38
Dockerfile Normal file
View File

@@ -0,0 +1,38 @@
FROM rockylinux/rockylinux:8
COPY el8.repo.internal.geedge.net.repo /tmp/repo.internal.geedge.net.repo
COPY netrc.conf /root/.netrc
COPY tsg_framework.sh /etc/profile.d/tsg_framework.sh
RUN cp /tmp/repo.internal.geedge.net.repo /etc/yum.repos.d/ && \
yum install -y gcc gcc-c++ make epel-release patch wget socat automake autoconf libtool rpm-build git yum-utils && \
wget -O /etc/yum.repos.d/epel.repo http://mirrors.aliyun.com/repo/epel-archive-8.repo && \
sed -i 's/epel-archive/epel/g' /etc/yum.repos.d/epel.repo && \
yum-config-manager --enable powertools && \
dnf --enablerepo=powertools install -y libpcap-devel && \
yum install -y cmake3 && \
yum install -y python2 && \
yum install -y python3-pip && \
pip3 install -i https://pypi.tuna.tsinghua.edu.cn/simple httpie && \
rpm -U https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/Packages/c/cppcheck-2.7-1.el7.x86_64.rpm && \
yum install -y sudo && \
yum install -y elfutils-libelf-devel libmnl-devel libnfnetlink-devel gtest-devel && \
yum install -y net-tools psmisc iproute initscripts gperftools-libs gdb snappy && \
yum install -y libunwind gperftools && \
dnf --enablerepo=powertools install -y libnsl
RUN yumdownloader --destdir=/tmp/ libMESA_prof_load-devel libMESA_prof_load \
libMESA_htable-devel libMESA_htable \
libMESA_handle_logger-devel libMESA_handle_logger \
libMESA_field_stat2-devel libMESA_field_stat2 \
libfieldstat3-devel libfieldstat3 libfieldstat4-devel libfieldstat4 \
libbreakpad_mini libMESA_jump_layer libcjson && \
find /tmp/ -name "*.rpm" |xargs rpm --prefix=/opt/tsg/framework --force --nodeps -ivh
RUN yumdownloader --destdir=/tmp/ sapp stellar-c && \
find /tmp/ -name "sapp*.rpm" |xargs rpm --prefix=/opt/tsg/sapp -ivh && \
find /tmp/ -name "stellar-c*.rpm" | xargs rpm --prefix=/opt/tsg/ -ivh
RUN yum clean all && \
rm -rf /var/cache/yum
CMD [ "/bin/bash" ]

105
README.md
View File

@@ -1,93 +1,40 @@
# stellar-dev-env
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://git.mesalab.cn/stellar/stellar-dev-env.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://git.mesalab.cn/stellar/stellar-dev-env/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
Stellar-Dev-Env is a tool based on GitLab CI that helps you build and release a Docker image for your stellar-c development environment quickly and easily.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
Step 1: Login to private docker registry, use the following command:
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
```
docker login https://git.mesalab.cn:7443 -u $your_username -p $your_passwd
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
```
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
Replace `your_username` and `your_passwd` with your private account.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Step 2: Pull the stellar-dev-env Docker image, use the following command:
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
```
docker pull git.mesalab.cn:7443/stellar/stellar-dev-env:main
```
## License
For open source projects, say how it is licensed.
After successfully pulling the image, you can use the stellar-dev-env Docker container as needed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
## Development Components
The stellar-dev-env Docker image comes pre-installed with essential development components, including:
* sapp
* stellar-c
* libMESA_htable
* ibMESA_handle_logger
* libMESA_prof_load
* libMESA_field_stat2
* libMESA_jump_layer
* libfieldstat3
* libfieldstat4
* libbreakpad_mini
* licjson

29
el8.repo.internal.geedge.net.repo Normal file
View File

@@ -0,0 +1,29 @@
[mesa-framework]
name=mesa-framework
baseurl=http://repo.internal.geedge.net/pulp/content/8/x86_64/stable/framework/
gpgcheck=0
[platform]
name=platform
baseurl=http://repo.internal.geedge.net/pulp/content/8/x86_64/stable/platform/
gpgcheck=0
[protocol]
name=protocol
baseurl=http://repo.internal.geedge.net/pulp/content/8/x86_64/stable/protocol/
gpgcheck=0
[tsg]
name=tsg
baseurl=http://repo.internal.geedge.net/pulp/content/8/x86_64/stable/tsg/
gpgcheck=0
[AppSketch]
name=AppSketch
baseurl=http://repo.internal.geedge.net/pulp/content/8/x86_64/stable/AppSketch/
gpgcheck=0
[stellar]
name=stellar
baseurl=http://repo.internal.geedge.net/pulp/content/8/x86_64/stable/stellar/
gpgcheck=0

3
netrc.conf Normal file
View File

@@ -0,0 +1,3 @@
machine repo.internal.geedge.net
login admin
password password

40
tsg_framework.sh Normal file
View File

@@ -0,0 +1,40 @@
if [ -z "$TSG_PLATFORM_SETUP" ]; then
#for c include
if [ "$C_INCLUDE_PATH" ]; then
export C_INCLUDE_PATH=/opt/tsg/framework/include:/opt/tsg/framework/include/MESA/:$C_INCLUDE_PATH
else
export C_INCLUDE_PATH=/opt/tsg/framework/include:/opt/tsg/framework/include/MESA/
fi
#for c++ include
if [ "$CPLUS_INCLUDE_PATH" ]; then
export CPLUS_INCLUDE_PATH=/opt/tsg/framework/include:/opt/tsg/framework/include/MESA/:$CPLUS_INCLUDE_PATH
else
export CPLUS_INCLUDE_PATH=/opt/tsg/framework/include:/opt/tsg/framework/include/MESA/
fi
#for linking
if [ "$LIBRARY_PATH" ]; then
if [[ ! -n `echo $LIBRARY_PATH | grep '/usr/local/lib'` ]];then
export LIBRARY_PATH=/opt/tsg/framework/lib/:/usr/local/lib/:$LIBRARY_PATH
else
export LIBRARY_PATH=/opt/tsg/framework/lib/:$LIBRARY_PATH
fi
else
export LIBRARY_PATH=/opt/tsg/framework/lib/:/usr/local/lib/
fi
#for ld
if [ "$LD_LIBRARY_PATH" ]; then
if [[ ! -n `echo $LD_LIBRARY_PATH | grep '/usr/local/lib'` ]];then
export LD_LIBRARY_PATH=/opt/tsg/framework/lib/:/usr/local/lib/:$LD_LIBRARY_PATH
else
export LD_LIBRARY_PATH=/opt/tsg/framework/lib/:$LD_LIBRARY_PATH
fi
else
export LD_LIBRARY_PATH=/opt/tsg/framework/lib/:/usr/local/lib/
fi
export TSG_PLATFORM_SETUP=1
fi