Главная страница » Football » Jordan » 1st Division

1st Division stats & predictions

Today

Bet on Key Players:

Diversifying Your BetsDiversifying your bets can help spread risk and increase your chances of winning. Consider placing multiple types of bets on each match, such as win/draw/lose, over/under goals, and specific player performances.

Fan Engagement and Social Media BuzzThe Role of Social Media in Football BettingSocial media platforms have become integral in shaping fan engagement and influencing betting trends. Fans share real-time updates, opinions, and predictions that can impact betting markets.

Influential Hashtags and Trends:timmyfaust/timmyfaust.github.io<|file_sep|>/README.md # timmyfaust.github.io This is my personal website/blog where I publish stuff. The website itself is built using [Jekyll](http://jekyllrb.com/) based off [Hyde](http://hyde.getpoole.com/). It uses [Bootstrap](http://getbootstrap.com/) for CSS styling. It also uses [Font Awesome](http://fortawesome.github.io/Font-Awesome/) for icons. And finally it uses [Highlight.js](https://highlightjs.org/) for code syntax highlighting. ## License The theme is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT). <|file_sep|># Site settings title: Timmy Faust - Personal Blog email: [email protected] description: "This is my personal blog." baseurl: "" url: "http://timmyfaust.com" twitter_username: timmyfaust github_username: timmyfaust # Build settings markdown: kramdown kramdown: input: GFM # Enable GitHub Flavored Markdown (!!!) syntax_highlighter: rouge # Use Rouge for syntax highlighting exclude: - Gemfile - Gemfile.lock - LICENSE.md highlighter: rouge # Analytics settings (optional) ga_tracking_id: # Disqus settings (optional) disqus_shortname: # Social settings (optional) social: - title: github url: http://github.com/timmyfaust/ - title: linkedin url: http://linkedin.com/in/timmyfaust/ - title: twitter url: http://twitter.com/timmyfaust/ # Navigation links (optional) navigation_links: - title: About me url: /about/ - title: Archive url: /archive/ <|repo_name|>timmyfaust/timmyfaust.github.io<|file_sep|>/_posts/2017-01-30-migrating-from-rackspace-cloud-files-to-amazon-s3.md --- layout: post title: "Migrating from Rackspace Cloud Files To Amazon S3" description: category: tags: --- {% include JB/setup %} I recently decided it was time I moved my website from Rackspace Cloud Files over to Amazon S3 since I wasn't using any other services from Rackspace anymore. The following steps should help anyone else migrating their static assets over. ## Download Files From Rackspace Cloud Files First thing you'll need is all your files downloaded from Rackspace Cloud Files so you can upload them somewhere else. You can use [Rackspace Cloud Files Explorer](https://github.com/rackerlabs/rackspace-cloud-files-explorer) which is pretty awesome: {% highlight bash %} $ git clone https://github.com/rackerlabs/rackspace-cloud-files-explorer.git $ cd rackspace-cloud-files-explorer/ $ npm install . $ ./cf-explorer.js --help Usage: ./cf-explorer.js [--options] command [args] Options: --access-key-id ACCESS_KEY_ID Your Rackspace Access Key ID --api-auth-url API_AUTH_URL API Authentication URL --api-url API_URL API URL --container CONTAINER Container name --domain DOMAIN Domain name --force Force download even if file exists --help Show help --max-download-attempts MAX_DOWNLOAD_ATTEMPTS Maximum number of download attempts before giving up --no-checksum Do not verify file checksums when downloading files --region REGION Region ID or Region Name --secret-key SECRET_KEY Your Rackspace Secret Key --timeout TIMEOUT Request timeout in milliseconds Commands: list List all objects in container get-file Download object from container delete-file Delete object from container create-container Create new container delete-container Delete container upload-file Upload file {% endhighlight %} So if you know your `access_key_id` and `secret_key` then you can download all your files like this: {% highlight bash %} $ ./cf-explorer.js get-file --access-key-id "YOUR_ACCESS_KEY_ID" --secret-key "YOUR_SECRET_KEY" --container "YOUR_CONTAINER_NAME" --domain "YOUR_DOMAIN" --recursive --download-directory "/tmp/static-assets/" {% endhighlight %} ## Install AWS CLI Next you'll want to install the AWS CLI so you can upload files directly into S3: {% highlight bash %} $ pip install awscli --upgrade --user $ export PATH=$PATH:$HOME/Library/Python/2.7/bin/ {% endhighlight %} ## Configure AWS CLI You'll need an AWS account so you can create an IAM user with `AmazonS3FullAccess` permissions. Then you'll want to run `aws configure`: {% highlight bash %} $ aws configure AWS Access Key ID [None]: YOUR_ACCESS_KEY_ID_HERE AWS Secret Access Key [None]: YOUR_SECRET_ACCESS_KEY_HERE Default region name [None]: us-east-1 # This is just an example region. Default output format [None]: json Your keys are now configured! {% endhighlight %} ## Upload To S3 Now it should be pretty straight forward how you upload all your files into S3: {% highlight bash %} $ aws s3 sync /tmp/static-assets s3://your-bucket-name-here/ --acl public-read --delete --exact-timestamps --metadata-directive REPLACE --cache-control 'max-age=31536000' # This sets caching rules so browsers don't keep requesting these files every time. {% endhighlight %} ## Update Website To Use New S3 Bucket URLs Finally you'll want to update your website so it references these new files hosted on Amazon S3 instead of Rackspace Cloud Files. For example if you're using Jekyll then update `_config.yml`: {% highlight yaml %} # Static site settings baseurl : "/static-assets" # This was pointing at Cloud Files previously. {% endhighlight %} To something like this: {% highlight yaml %} # Static site settings baseurl : "//your-bucket-name-here.s3.amazonaws.com" # This points at Amazon S3 now. {% endhighlight %} That should do it! **UPDATE**: There are also tools out there like [CloudBerry Explorer](https://www.cloudberrylab.com/free-tools) which also work really well.<|repo_name|>timmyfaust/timmyfaust.github.io<|file_sep|>/_posts/2017-03-19-scaling-rails-applications-with-kubernetes-and-rails-sidekiq.md --- layout: post title: "Scaling Rails Applications With Kubernetes And Rails Sidekiq" description: category: tags: --- {% include JB/setup %} I've been working with Kubernetes recently on how best scale Rails applications using Sidekiq as a background job processor. I've already written about how I use Docker Compose locally ([see here](https://timmyfaust.com/blog/docker-compose-local-rails-sidekiq)) but I wanted something similar when running production apps. Kubernetes makes it easy because it handles all scaling automatically using `replicas` when using something like `Deployment`s. The setup below works well because we have one `Deployment` per Rails application component which are connected together using `Service`s which abstract away all networking concerns between containers. The following diagram shows how everything connects together when running multiple Rails applications within Kubernetes:  Here is what each component does within Kubernetes: * **Rails Web Server Deployment** - Scales up/down automatically based on load using multiple replicas which handle HTTP requests via Nginx. * **Sidekiq Worker Deployment** - Scales up/down automatically based on load using multiple replicas which handle background jobs via Sidekiq. * **Postgres Deployment** - Runs Postgres as single instance inside Kubernetes pod using persistent volume claims. * **Redis Deployment** - Runs Redis as single instance inside Kubernetes pod using persistent volume claims. * **Nginx Deployment** - Acts as reverse proxy handling SSL termination via LetsEncrypt TLS certificates. * **Sidekiq UI Deployment** - Runs Sidekiq UI server for viewing background job progress within browser. * **Fluentd Deployment** - Collects logs from containers within pods into Elasticsearch service which handles search queries via Kibana web app. Here are some useful links about Kubernetes deployments: * https://kubernetes.io/docs/user-guide/deployments/ * https://kubernetes.io/docs/user-guide/pod-states/#container-probes ## Rails Web Server Deployment This is what our Rails web server deployment looks like: yaml apiVersion: extensions/v1beta1 # Use v1beta1 because it has 'replicas' field whereas v1alpha1 doesn't have this field yet. kind: Deployment # Deployments are used when we want automatic scaling up/down based on load. metadata: name: rails-web-server # Name used when referring this deployment within Kubernetes cluster. labels: app.kubernetes.io/name : rails-web-server # Labels are used when filtering resources based on criteria we specify. spec: replicas : {{WEB_SERVER_REPLICAS}} # Scale up/down based on load using multiple replicas. template: metadata: labels: app.kubernetes.io/name : rails-web-server # Labels are used when filtering resources based on criteria we specify. spec: containers : - name : rails-web-server-container # Name used when referring this container within Kubernetes cluster. image : {{WEB_SERVER_IMAGE}} # Image location used when building Docker images for running inside Kubernetes cluster. ports : - containerPort : {{WEBSERVER_PORT}} # Port exposed by Rails web server inside container listening on localhost only within Kubernetes cluster network space only! envFrom : - configMapRef : name : rails-web-server-config-map # Config map containing environment variables used by Rails web server container running inside Kubernetes cluster network space only! Note we're using `extensions