投稿時間:2023-08-14 14:14:13 RSSフィード2023-08-14 14:00 分まとめ(16件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
ROBOT	ロボスタ	生成系AIはクリエイターの仕事を奪うのか? 少ない言葉で高精度な画像を描く驚異の技術「SeaArt」AIによるコンテンツ生成を語る	https://robotstart.info/2023/08/14/seaart-report.html	生成系AIはクリエイターの仕事を奪うのか少ない言葉で高精度な画像を描く驚異の技術「SeaArt」AIによるコンテンツ生成を語るシェアツイートはてブSTARCLUSTERPTELTDは、同社が運営するAI絵画プラットフォーム「SeaArt」をより正式的に日本市場に向けてサービスを開始した。	2023-08-14 04:38:49
IT	ITmedia 総合記事一覧	[ITmedia Mobile] TP-Link、5G対応SIMフリーメッシュWi-Fi 6ルーター「Deco X50-5G」発売	https://www.itmedia.co.jp/mobile/articles/2308/14/news091.html	decoxg	2023-08-14 13:17:00
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	WHI、自治体向け人事クラウド「COMPANY on LGWAN」の対象を正職員に拡大、非常勤と両対応に | IT Leaders	https://it.impress.co.jp/articles/-/25224	companyonlgwan	2023-08-14 13:37:00
python	Pythonタグが付けられた新着投稿 - Qiita	error in ml_metrics setup command: use_2to3 is invalid. の対処法	https://qiita.com/pi-man/items/f9ab794c9fb8aecd2d1d	pythonse	2023-08-14 13:45:27
python	Pythonタグが付けられた新着投稿 - Qiita	マルチスレッド処理をやってみる（Python）	https://qiita.com/Moore_Ca/items/89d78bb152de405b73b2	codemacstudio	2023-08-14 13:38:48
Azure	Azureタグが付けられた新着投稿 - Qiita	SAP on Azure デプロイ自動化フレームワーク - ワークロードゾーン作成	https://qiita.com/R3ne7/items/5fb283ff2efdb4a7a505	作業内容	2023-08-14 13:18:21
Git	Gitタグが付けられた新着投稿 - Qiita	【備忘録】GithubのSSH生成・設定と接続方法	https://qiita.com/kuro_maru/items/ac3d06b3fadf2009f210	github	2023-08-14 13:49:05
技術ブログ	Developers.IO	CDK(Cloud Development Kit)を始めましょう!	https://dev.classmethod.jp/articles/cdkcloud-development-kit/	cdkclouddevelopmentkit	2023-08-14 04:15:53
技術ブログ	Developers.IO	Snowcone でファイルサーバを FSx に移行する場合の選択肢を教えてください	https://dev.classmethod.jp/articles/tsnote-snowcone-migrate-file-server-to-fsx/	fsxforwindowsfileser	2023-08-14 04:14:03
技術ブログ	Developers.IO	AWS Backupでタグに空白を含む場合に、期待通りに動かなかったときの原因と対処	https://dev.classmethod.jp/articles/backup-multi-tag/	awsbackup	2023-08-14 04:09:34
海外TECH	DEV Community	Getting Started with Svelte: A Refreshingly Different Approach to Web Development	https://dev.to/ironside/getting-started-with-svelte-a-refreshingly-different-approach-to-web-development-35j1	Getting Started with Svelte A Refreshingly Different Approach to Web Development Getting Started with Svelte A Refreshingly Different Approach to Web DevelopmentAre you tired of the JavaScript frameworks that come with a hefty bundle size and complex setup If so let s dive into Svelte a revolutionary approach to building web applications that challenges the conventional wisdom of front end development Why Svelte Svelte takes a different route by shifting the heavy lifting from the browser to the compilation step Instead of shipping a bulky runtime library to the client Svelte compiles components into highly efficient vanilla JavaScript during build time This means your users download smaller files and your applications run faster The Svelte Compiler MagicSvelte introduces a compiler that analyzes your components and generates optimized code It compiles away abstractions leaving you with clean and performant JavaScript This process is so seamless that it might feel like magic Creating Your First Svelte ComponentLet s jump in by creating a simple interactive component In Svelte a component consists of three main parts the lt script gt lt style gt and lt svelte gt tags The lt script gt tag is where you define your component s logic You can use reactive declarations to automatically update the DOM whenever your variables change The lt style gt tag contains your component s styling It uses regular CSS syntax to style your component s elements The lt svelte gt tag holds the HTML structure of your component Example Creating a Button ComponentLet s create a button that counts the number of times it s clicked lt script gt let count function handleClick count lt script gt lt style gt button padding px px background color bff color white border none cursor pointer lt style gt lt svelte gt lt button on click handleClick gt Clicked count count time times lt button gt lt svelte gt ConclusionSvelte challenges the traditional approach to front end frameworks offering a clean and efficient alternative By compiling components into optimized JavaScript Svelte reduces runtime overhead and makes your applications faster In our next installment we ll explore Svelte components in more detail and learn how to create reusable building blocks for your web applications Stay tuned as we embark on this journey to discover the power and simplicity of Svelte Your web development experience is about to be transformed	2023-08-14 04:40:25
海外TECH	DEV Community	Docker Compose Logs: Guide & Best Practices	https://dev.to/squadcast/docker-compose-logs-guide-best-practices-1b2k	Docker Compose Logs Guide amp Best PracticesDocker Compose is a tool for defining and running multi container Docker applications It allows developers to streamline the process of configuring building and running multiple containers as a single unit with a docker compose yml This configuration file specifies the services networks and volumes required for an application and their relationships and dependencies The docker compose logs command displays the logs of all services defined in the docker compose yml file It helps monitor and debug applications by providing insights into the behavior and performance of the various services The command aggregates the logs from all the containers specified in the docker compose yml file presenting them in a unified view By default the logs are shown in the order they were generated but you can filter or customize the output using various flags and options such as follow or f Follow log output similar to tail f timestamps or t Show timestamps in the log output tail Show the last N lines of logs where N is the number you provide SERVICE Specify one or more services to display logs for instead of showing logs for all services This article will explore Docker Compose logging drivers and logging strategy best practices practical examples of debugging and troubleshooting using Docker logs and demonstrate how to set up log streaming Summary of key Docker Compose logs conceptsThe table below summarizes key Docker Compose logs concepts this article will build upon Concept docker compose logsDescription docker compose logs is a Docker command used to view the container logs for a system s defined services Concept Logging driversDescription Docker supports several logging drivers that define how your container logs are collected and stored Concept Logging strategiesDescription There are two log delivery modes in Docker blocking and non blocking Concept Debugging with logsDescription The docker logs command allows you to inspect specific containers and review logs that could provide insight into the issue your application is facing Concept Storing logsDescription Maintaining a healthy system requires a clear understanding of log locations and adherence to lifecycle policy guidelines Docker logging driversLogging drivers are plugins that handle container logs in Docker They define how logs are collected processed and stored for a container Each driver provides different features and is designed to work with various logging services and platforms The default logging driver in Docker Compose is the json file driver This driver stores logs as JSON files on the host machine where the container is running However Docker supports several other logging drivers you can configure in your Docker Compose setup To configure Docker Compose to use separate logging drivers specify the desired driver in the docker compose yml file using the logging configuration option for each service Here s an example version services web image my web app logging driver gelf options gelf address udp logstash host tag my web app db image my db logging driver fluentd options fluentd address fluentd host tag my db In this example the web service is configured to send logs to a Logstash server in the ELK stack using the gelf logging driver The gelf address option is set to the address of the Logstash server which is configured to listen for GELF input on port you need to configure Logstash accordingly The db service is configured to send logs to a Fluentd server using the fluentd logging driver The fluentd address option is set to the address of the Fluentd server which listens on port default Fluentd port Before using this configuration ensure you have the ELK stack and Fluentd servers set up and properly configured to receive logs from your Docker containers Docker Compose logging strategiesThe log delivery mode in Docker determines how logs are transferred from the running containers to the specified log driver There are two delivery modes Blocking In this mode the Docker daemon can block a container preventing it from writing to the log driver This is especially useful if the log driver cannot keep up with the amount of logs being written However it can also cause issues if the blocked container is a critical part of your application Non blocking Docker will not block containers in this mode even if the log driver cannot keep up with the amount of logs being written Instead Docker will buffer the logs and deliver them when the log driver is ready However this can cause issues if the log buffer fills up causing Docker to drop logs To understand the risk of log loss with non blocking mode suppose you have a Docker Compose file docker compose yml that defines two services a web server and a database The web server logs important information to stdout or stderr within the container and you expect these logs to be available for debugging or monitoring purposes version services web build ports db image mysql latestenvironment MYSQL ROOT PASSWORD passwordIf you start the services using docker compose up d in non blocking mode detached mode the containers will run in the background However if you don t actively capture or redirect the logs to a file or logging system the logs will not be immediately visible or persisted This can lead to potential log loss Four essential Docker Compose logs best practicesThere is no one size fits all Docker Compose logging strategy However several well established best practices can help you define the right strategy for specific use cases Here are four key Docker Compose logging best practices to consider Use a centralized logging solution Instead of relying solely on docker compose logs consider using a centralized logging system to aggregate and manage logs from multiple containers and services Popular options include the ELK Stack Elasticsearch Logstash and Kibana Graylog or Fluentd Configure logging drivers Docker provides various logging drivers that allow you to send container logs to different destinations When using Docker Compose you can specify a logging driver for each service in your docker compose yml file Choose a logging driver that fits your needs such as json file syslog journald or fluentd Consider log rotation and retention Containers can generate a significant amount of logs consuming disk space over time Implement log rotation and retention strategies to manage log files effectively For example you can configure the maximum log file size max size and the number of retained log files max file in the logging driver options This helps to control disk usage and prevent log files from growing indefinitely Include relevant information in logs Ensure that the logs emitted by your application or services include sufficient information for troubleshooting Include timestamps request response details error codes stack traces and other relevant contextual information This makes it easier to understand and diagnose issues when reviewing the logs Integrated full stack reliability management platform Try For Free Drive better business outcomes with incident analytics reliability insights SLO tracking and error budgets Manage incidents on the go with native iOS and Android mobile apps Seamlessly integrated alert routing on call and incident response How to debug with Docker Compose logsDebugging a containerized application using Docker Compose logs can be very efficient especially when dealing with HTTP error codes HTTP is a generic error message indicating that the server encountered an unexpected condition that prevented it from fulfilling the request Here is a step by step guide for debugging HTTP errors with Docker Compose logs Identify the affected container The first step is identifying the container causing the issue If you re using Docker Compose you can use the docker compose ps command to list all running containers The output will give you the container ID and its status docker compose psView the logs Once you have identified the problematic container you can view its logs using the docker logs command followed by the container ID or name This will display the logs for that particular container Look for any error messages or stack traces related to the HTTP error docker logs Filter the Logs If you re dealing with a large number of logs it can be helpful to filter them You can use the grep command to filter the logs for specific keywords For example to filter logs for you can use docker logs gt amp grep This will display only the logs that contain the keyword Continuous log tracking If the issue is still occurring and you need to track logs continuously you can use the f or follow option with the docker logs command docker logs f docker logs follow This will continuously display the logs as they are generated Look for any patterns or recurring error messages Debug the issue You can start debugging the issue based on the error messages and stack traces in the logs This might involve checking your application code configuration files database connections or external services with which your application interacts Inspect the container If you cannot diagnose the issue with logs alone you can inspect the container s metadata for clues Use the docker inspect command to get more information about the container like its environment variables volumes network settings etc docker inspect Storing Docker Compose logsLogs in Docker are typically stored on the host system where the Docker daemon runs The exact location and format depend on the Docker logging driver For example if you re using the default json file driver the logs are stored in JSON format at the following location var lib docker containers json logIf you re using a different logging driver like syslog or journald the logs are stored in the location determined by that system s configuration Lifecycle policy guidelinesManaging logs is a critical task in maintaining the health of your system Here are some guidelines for creating a lifecycle policy based on the aggregate size of logs Monitor log sizes Regularly monitor the aggregate size of your logs Tools like du in Unix can help you with this task You can also configure alerts in your monitoring system to notify you when logs reach a certain size Set a maximum log size Determine a maximum size for your logs This will depend on your system s capacity and how critical logs are to your operations For example you might decide that logs should never take up more than of your disk space Implement log rotation Log rotation involves renaming current log files and starting a new one This prevents individual log files from becoming too large Docker has built in log rotation for the json file and journald log drivers You can specify the maximum file size and the number of files to keep Archive important old logs If old logs are still necessary e g they are required for compliance consider archiving them Archived logs can be compressed to save space and moved to cheaper storage options Delete unimportant old logs If old logs are not needed delete them This can be done manually or by using a log management tool Be careful not to delete logs that might be needed for auditing or troubleshooting purposes Automate log management Consider using log management tools or services that can automate these tasks For example Logrotate on Linux can automatically rotate compress and delete logs Managed services like AWS CloudWatch or Google Stackdriver can also handle log lifecycle management How to troubleshoot common issues with Docker Compose logsIf you re working with a multi container Docker environment and experiencing issues Docker Compose logs can be extremely useful for troubleshooting Below is a step by step guide on troubleshooting with Docker Compose logs using a real world example of a Python Flask application with a PostgreSQL database Assume your docker compose yml file looks like this version services web build command python app py volumes codeports depends on dbdb image postgres environment POSTGRES USER postgresPOSTGRES PASSWORD postgresPOSTGRES DB test dbSuppose you notice that your application is not responding as expected and you suspect an issue with the database connection You can follow the steps below to debug Check the logs for the web serviceFirst check the logs for the web service which is where the application is running If you see an error message related to the database connection such as OperationalError psycopg OperationalError could not connect to server Connection refusedThis indicates that the application is unable to connect to the database Check the logs for the database serviceNext check the logs for the database service to see if there are any issues there docker compose logs dbModify the Docker Compose fileBased on the error message you may have specified the wrong password for the PostgreSQL user in your docker compose yml file In this case you d need to correct the password and run docker compose up again ‍ Follow the logsIf you re still experiencing issues following the logs in real time as you interact with the application could be helpful You can do this with the f or follow option docker compose logs fFilter the logsYou can filter the logs using grep to find a specific error or message For example to find log entries that contain the word error you could run docker compose logs web grep error Example of log streaming using celery socket IO and containersIn this example we provide a sample application demonstrating log streaming between containers and why it is important We have two components A server that accepts HTTP POST requestsA client that sends HTTP POST requestsThe client sends a POST request to the server to calculate the Fibonacci sequence The server then computes the sequence and sends back the response This simple model could be further extended to distribute all sorts of workloads as microservices SetupThe following docker compose yml file represents the setup described above version services redis image redis ports web build servercommand flask run host port volumes server codeports environment FLASK APP app server pyFLASK RUN HOST CELERY BROKER URL redis redis CELERY RESULT BACKEND redis redis depends on redisworker build server command celery A tasks celery worker loglevel infocommand celery A tasks worker loglevel infovolumes server codeenvironment CELERY BROKER URL redis redis CELERY RESULT BACKEND redis redis depends on webclient build context clientdockerfile Dockerfilevolumes client codedepends on workerThe docker compose yml file above creates four containers redis worker and web constitute the server component and the client is a separate component For simplicity s sake to avoid “ not found errors we added the depends on key to the client image so that the client sends the request only after the server is fully up Once all the containers are up the client sends a POST request with a single parameter n to compute Fibonacci sequence up until n Fibonacci numbers For example if the parameter n is the sequence would be Each Fibonacci number the server calculates is sent to the client as a log emission This behavior is helpful when a client issues a long running command to the server and instead of waiting at a blank screen the server can emit feedback logs Celery workers are used to hand off compute intensive or long running tasks that can be processed asynchronously Celery requires a message broker in this case Redis to facilitate communication between the task producer the client application and the task consumer the worker The complete code for the application above is available at SummaryDocker Compose enables the configuration building and running of multi container Docker applications using a YAML configuration file docker compose yml Developers can monitor applications by displaying logs of all defined services with the docker compose logs command Docker supports various logging drivers that process and store container logs Docker s log delivery modes blocking and non blocking affect how logs are transferred from containers to the specified log driver Debugging with logs can be efficient in identifying issues such as “HTTP error codes Logs are stored based on the logging driver used and it s essential to have a log lifecycle policy to manage the aggregate size of logs Docker Compose logs are also useful for troubleshooting in a multi container environment Real time log streaming can provide client feedback for long running tasks processed asynchronously by server side Celery workers	2023-08-14 04:25:29
ニュース	BBC News - Home	The Papers: Baby in 'tent terror' and poor pupils 'hit hardest'	https://www.bbc.co.uk/news/blogs-the-papers-66494567?at_medium=RSS&at_campaign=KARANGA	pembrokeshire	2023-08-14 04:53:22
ニュース	Newsweek	「女子スポーツ」とは何か？...トランスジェンダー選手との競争は本当に「フェア」なのか	https://www.newsweekjapan.jp/stories/culture/2023/08/post-102412.php	こんなことが起きているのは、性自認が女性の生物学的男性が女子種目に出場することを、CIACが認めたためだ。	2023-08-14 13:20:18
IT	週刊アスキー	【今週の注目】ケンタお得な10ピースパック、松屋の“ガパオ”など	https://weekly.ascii.jp/elem/000/004/149/4149760/	発売	2023-08-14 13:30:00
ニュース	THE BRIDGE	IBMとNASA、共同開発した地理空間基盤AIモデルをHugging Face上でオープンソース公開	https://thebridge.jp/2023/08/ibm-and-nasa-deploy-open-source-geospatial-ai-foundation-model-on-hugging-face	IBMとNASA、共同開発した地理空間基盤AIモデルをHuggingFace上でオープンソース公開HuggingFace上で利用可能なオープンソースのモデルはたくさんあるが、月日にもうつ加えられた。	2023-08-14 04:00:58